CMake/Utilities/Release
Brad King b377c8ac72 ENH: Do not include experimental WXDialog in release. 2006-07-21 15:20:42 -04:00
..
CMake.nsi.in ENH: removed the add to path 2005-12-13 14:07:25 -05:00
CMakeInstall.bmp ENH: added our own bitmap 2005-06-28 15:00:36 -04:00
MakeRelease.cmake.in BUG: fix space in path probs 2005-10-28 11:51:44 -04:00
README BUG: Added missing release steps. 2006-06-26 09:46:22 -04:00
Release.cmake BUG: Do not install MSVC dlls for a non-MSVC build. 2006-02-16 20:15:03 -05:00
cmake_login ENH: more stuff 2006-05-02 16:41:06 -04:00
cmake_release.sh.in ENH: 2006-01-09 12:46:13 -05:00
config_AIX Merging release script changes from 1.8 branch to main tree. 2003-08-27 16:08:11 -04:00
config_CYGWIN_NT-5.1 ENH: merge changes from branches 2005-07-11 17:12:17 -04:00
config_Darwin ENH: Do not include experimental WXDialog in release. 2006-07-21 15:20:42 -04:00
config_HP-UX move release stuff off branch 2005-07-12 17:22:41 -04:00
config_IRIX64 ENH: merge changes from branches 2005-07-11 17:12:17 -04:00
config_Linux ENH: merge changes from branches 2005-07-11 17:12:17 -04:00
config_OSF1 Merging release script changes from 1.8 branch to main tree. 2003-08-27 16:08:11 -04:00
config_SunOS move release stuff off branch 2005-07-12 17:22:41 -04:00
create-cmake-release.cmake ENH: release scripts 2006-05-19 15:53:42 -04:00
cygwin-package.sh.in ENH: merge changes from branches 2005-07-11 17:12:17 -04:00
dashmacmini2_release.cmake ENH: release scripts 2006-05-19 15:53:42 -04:00
dashsgi1_release.cmake ENH: 2006-05-10 14:03:51 -04:00
dashsgi1_release64.cmake ENH: 2006-05-10 14:03:51 -04:00
dashsun1_release.cmake ENH: works 2006-05-09 17:18:46 -04:00
destiny_release.cmake ENH: working package creator 2006-05-11 16:07:42 -04:00
hythloth_release.cmake ENH: change name to MAKE_COMMAND 2006-05-08 16:50:17 -04:00
muse_release.cmake ENH: skip bootstrap test as it already does a bootstrap 2006-05-08 16:59:48 -04:00
muse_release64.cmake ENH: add 64 bit sgi 2006-05-09 13:48:36 -04:00
release_cmake.cmake ENH: extra path 2006-05-14 15:24:57 -04:00
release_cmake.sh.in ENH: working package creator 2006-05-11 16:07:42 -04:00
release_dispatch.sh move release stuff off branch 2005-07-12 17:22:41 -04:00
v60n177_aix_release.cmake ENH: extra path 2006-05-14 15:24:57 -04:00
vogon_release.cmake ENH: working package creator 2006-05-11 16:07:42 -04:00

README

1. Update Version information
  - change version in CMakeLists.txt
  - build on windows, and do a make; make install; make release // this step tags 
    - this changes cmake_release.sh
  * for major release edit   Source/cmCPluginAPI.h 

2. Update the FAQ with the current release.
3. Update hythloth:~kingb/Nightly/Scripts/util.CMakeWeb to generate web page docs for the new version.


NOTES from Brad:

The release scripts are located in CMake and ParaView under the Utilities/Release directory.  It is important to run the script obtained by checking out a copy of the corresponding release branch from CVS. Here is a summary of how to use them:


The release_dispatch.sh script has a list of machine names at the top. When run, this script will automatically ssh to these machines to build the releases.  Run it like this:


./release_dispatch.sh clean
./release_dispatch.sh binary
./release_dispatch.sh logs


The first line will ssh to all the machines and wipe out any existing release build.  The second will ssh to the machines and start the release scripts with output going to a log file.  The third line will bring up a whole bunch of xterm windows each showing the log from one of the machines.  Therefore you should run this from a prompt with access to an X display.  Alternatively you can just look at the log files manually.


After the logs report the job is complete, then the binaries should be sitting on the local machine in the same directory as the scripts.  You can run


./cmake_release.sh remote_source localhost


to get the source tarballs.  Then run


./cmake_release.sh upload


to upload the files to public in the proper FTP directory.


For shannara, the home directory does not have enough disk space to build ParaView.  After the "clean" step, you should manually log into the machine and do


rm -rf /disk2/ParaViewReleaseRoot
ln -s /disk2/ParaViewReleaseRoot ~/


For the aix build, you need to manually login to the box and checkout a copy of the Utilities/Release directory.  Then run the release script by hand:


./cmake_release.sh binary_tarball
./paraview_release.sh binary_tarball


Then in the release root directory there will be a Tarballs subdirectory with the binaries.