| 69 | | These procedures are given for a particular release manager's machine. The plan is to replace them with more generic procedures over time. |
| 70 | | |
| 71 | | * Create folders for export: |
| 72 | | |
| 73 | | c:\boost\boost_1_28_0 |
| 74 | | c:\boost\temp\boost_1_28_0 |
| 75 | | |
| 76 | | Note that several batch files assume these locations and naming schemes. |
| 77 | | |
| 78 | | * Export Win32 distribution: WinCVS | Remote | Checkout Module |
| 79 | | |
| 80 | | Checkout settings: module name and path on the server: boost, local folder to checkout to: c:\boost\boost_1_28_0 |
| 81 | | [for 1.29.0 export, put everything in a boost_1_29_0/boost subdirectory. Experiments with 1.30.0 tried boost/boost as the path on server, but that just resulted in getting the boost header subdirectory only.] |
| 82 | | |
| 83 | | Checkout options: (check) By revision/tab/branch: Version_1_28_0, (check) Do not create CVS directories (export) |
| 84 | | |
| 85 | | This results in the follow command: cvs -z9 export -r Version_1_28_0 boost (in directory C:\boost\boost_1_28_0) |
| 86 | | |
| 87 | | (takes about ten minutes) |
| 88 | | |
| 89 | | (rename boost-root if needed !!!!!!!!!!!!!!!!!!!) |
| 90 | | |
| 91 | | * Export Unix distribution: similar to above, except target is c:\boost\temp\boost_1_28_0 and set global for UNIX nl. |
| 92 | | |
| 93 | | * !!!!!! VERY IMPORTANT: WinCVS | Set Preferences | Global back to non-UNIX nl. !!!!!!!!!!!!!!! |
| 94 | | |
| 95 | | * Add regression results web pages into package (new in 1.33 so this is just a shot at the process - jeff) |
| 96 | | download all the regression results from website (may need meta-comm help on this) |
| 97 | | unpack the regression results into tools/regression/latest_release |
| 98 | | |
| 99 | | * General ZIP and TAR.GZ files |
| 100 | | |
| 101 | | n_n_n is 1_28_0 or whatever |
| 102 | | |
| 103 | | cd \boost |
| 104 | | boost_zip 1_21_2 (creates zip.log) |
| 105 | | boost_tar_gz 1_21_2 |
| 106 | | bash |
| 107 | | gunzip -c boost_1_21_2.tar.gz | bzip2 > boost_1_21_2.tar.bz2 |
| 108 | | exit |
| 109 | | |
| 110 | | * Upload and unpack the .zip release candidate to a SourceForge web services sub-directory. Post a message to the main list asking developers to check contents. (Daniel Frey has volunteered to help check). |
| 111 | | |
| 112 | | * Upload files for SourceForge release incoming directory using WS_FTP Pro |
| | 57 | * Upload files for SourceForge release incoming directory using WS_FTP Pro |
| 164 | | * Post a message announcing the release and recapping "Latest News". Post as separate messages to: boost, boost-announce, boost-users, comp.lang.c++.moderated, c++std-news@research.att.com |
| | 82 | * Post a message announcing the release and recapping "Latest News". Post as separate messages to: boost, boost-announce, boost-users, comp.lang.c++.moderated, c++std-news |
| | 83 | |
| | 84 | * Ready trunk/index.html, trunk/boost/version.hpp, and trunk/Jamroot for the next release and commit to Subversion. |
| | 85 | |
| | 86 | * Merge version number changes to branches/release. |
| 166 | | * Using the SourceForge shell services (sf_shell_svc.bat), cd /home/groups/b/bo/boost/htdocs, and rename regression tests as necessary. |
| 167 | | |
| 168 | | * Burn "Key Directories" CD for off-site backup. |
| 169 | | |
| 170 | | * Make sure CVS working copy is updated to main branch! |
| 171 | | |
| 172 | | * Ready root/index.htm, root/boost/version.hpp, root/Jamfile.v2 and root/Jamrules for the next release and commit to CVS so developers have a place to add "Latest news" blurbs. |
| 173 | | |
| 174 | | * Delete obsolete files from yahoogroups files section. |
| 175 | | |
| 176 | | Copyright Beman Dawes 2001 |
| | 88 | ---- |
| | 89 | Copyright Beman Dawes 2001, 2008 |
