| 1 | Copyright 2003, 2005, 2006 Vladimir Prus |
|---|
| 2 | Distributed under the Boost Software License, Version 1.0. |
|---|
| 3 | (See accompanying file LICENSE_1_0.txt or http://www.boost.org/LICENSE_1_0.txt) |
|---|
| 4 | |
|---|
| 5 | |
|---|
| 6 | Boost.Build V2 release procedure. |
|---|
| 7 | |
|---|
| 8 | [ Must be done from a Unix shell ] |
|---|
| 9 | |
|---|
| 10 | 0. Look for all issues for current milestone in the tracker. Close the fixed one, |
|---|
| 11 | if not already closed. Move to a later milestone, or fix all the unfixed |
|---|
| 12 | ones. |
|---|
| 13 | |
|---|
| 14 | Make sure that "bjam --version" output is correct. Update version string if |
|---|
| 15 | needed. Update bjam version and the version check is necessary. |
|---|
| 16 | Check the download locations in "index.html". Check that "last modified" |
|---|
| 17 | strings in docs are correct. |
|---|
| 18 | |
|---|
| 19 | 1. Make sure you don't have any local modification, and tag the CVS tree with |
|---|
| 20 | Milestone_X tag. Be sure to tag both Boost.Build and Boost.Jam sources. |
|---|
| 21 | |
|---|
| 22 | 2. Run |
|---|
| 23 | |
|---|
| 24 | cvs -d :ext:<your_user_name>@boost.cvs.sourceforge.net:/cvsroot/boost co -r |
|---|
| 25 | Milestone_X -P -d boost-build boost/tools |
|---|
| 26 | |
|---|
| 27 | Note: it turns out that anonymous CVS access uses some backup server, which |
|---|
| 28 | is not up-to-date. |
|---|
| 29 | |
|---|
| 30 | 3. Go to "boost-build/build/v2" directory. |
|---|
| 31 | |
|---|
| 32 | 4. Run "./roll.sh". This will create "boost-build.zip" and |
|---|
| 33 | "boost-build.tar.bz2" in parent directory, and also upload |
|---|
| 34 | new docs to sourceforge. |
|---|
| 35 | |
|---|
| 36 | 5. Unpack "boost-build.tar.bz2", and build jam. |
|---|
| 37 | |
|---|
| 38 | 6. Go to "test" and copy "test-config-example.jam" to "test-config.jam". |
|---|
| 39 | If you're not ghost, edit test-config.jam to specify all the right paths. |
|---|
| 40 | Run gcc tests: |
|---|
| 41 | |
|---|
| 42 | python test_all.py gcc --extras |
|---|
| 43 | |
|---|
| 44 | 7. Build all projects in examples-v2, using the bjam binary created at step 4. |
|---|
| 45 | Note: "threading=multi" might be needed to build QT examples. |
|---|
| 46 | |
|---|
| 47 | 8. Make SF release: |
|---|
| 48 | |
|---|
| 49 | - Go to |
|---|
| 50 | https://sourceforge.net/project/admin/editpackages.php?group_id=7586 |
|---|
| 51 | |
|---|
| 52 | - Create new Boost.Build release. Name it 2.0-mXX |
|---|
| 53 | |
|---|
| 54 | - Upload the changelog. Be sure to turn the "Preserve my pre-formatted |
|---|
| 55 | text" checkbox. |
|---|
| 56 | |
|---|
| 57 | - Rename previously built packages to boost-build-2.0-mXX.tar.bz2 |
|---|
| 58 | and boost-build-2.0-mXX.zip. Upload them to the |
|---|
| 59 | /incoming directory on ftp://upload.sourceforge.net |
|---|
| 60 | |
|---|
| 61 | - Add those file to release, edit file properties. |
|---|
| 62 | |
|---|
| 63 | - In a separate browser, verify changelog is not damaged. |
|---|
| 64 | |
|---|
| 65 | - In a separate browser, Download the files and verify checksums. |
|---|
| 66 | |
|---|
| 67 | - In SF file release interface, send email notice. |
|---|
| 68 | |
|---|
| 69 | 9. Announce the release, etc. |
|---|
| 70 | |
|---|
| 71 | 10. Login to SF and update the current-release redirects in |
|---|
| 72 | /home/groups/b/bo/boost/htdocs/boost-build2/.htaccess. |
|---|
| 73 | |
|---|
| 74 | 11. If any issues were found during release in this document or in |
|---|
| 75 | test-config-example.jam, commit those changes. The release need |
|---|
| 76 | not be redone, but changes must be comitted. |
|---|
| 77 | |
|---|
| 78 | 12. Set release date in changes.txt and commit. |
|---|
| 79 | |
|---|
