ceph/src/boost/tools/build/notes/release_procedure.txt

   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    string in index.html is correct.
  18
  19 1. Make sure you don't have any local modification, and create SVN directory
  20
  21         https://svn.boost.org/svn/boost/branches/build/Milestone_X
  22
  23    Then, copy:
  24
  25         https://svn.boost.org/svn/boost/trunk/tools/build
  26         https://svn.boost.org/svn/boost/trunk/tools/jam
  27
  28    to that directory.
  29
  30 2. Run
  31
  32    svn co https://svn.boost.org/svn/boost/branches/build/Milestone_X boost-build
  33
  34 3. Go to "boost-build/build/v2" directory.
  35
  36 4. Run "./roll.sh". This will create "boost-build.zip" and
  37    "boost-build.tar.bz2" in parent directory, and also upload
  38    new docs to sourceforge.
  39
  40 5. Unpack "boost-build.tar.bz2", and build jam.
  41
  42 6. Go to "test" and copy "test-config-example.jam" to "test-config.jam".
  43    If you're not ghost, edit test-config.jam to specify all the right paths.
  44    Run gcc tests:
  45
  46       python test_all.py gcc --extras
  47
  48 7. Build all projects in examples-v2, using the bjam binary created at step 4.
  49    Note: "threading=multi" might be needed to build QT examples.
  50
  51 8. Make SF release:
  52
  53    - Go to
  54      https://sourceforge.net/project/admin/editpackages.php?group_id=7586
  55
  56    - Create new Boost.Build release. Name it 2.0-mXX
  57
  58    - Upload the changelog. Be sure to turn the "Preserve my pre-formatted
  59      text" checkbox.
  60
  61    - Rename previously built packages to boost-build-2.0-mXX.tar.bz2
  62      and boost-build-2.0-mXX.zip. Upload them to the
  63      /incoming directory on ftp://upload.sourceforge.net
  64
  65    - Add those file to release, edit file properties.
  66
  67    - In a separate browser, verify changelog is not damaged.
  68
  69    - In a separate browser, Download the files and verify checksums.
  70
  71    - In SF file release interface, send email notice.
  72
  73 9. Announce the release, etc.
  74
  75 10. Login to SF and update the current-release redirects in
  76     /home/groups/b/bo/boost/htdocs/boost-build2/.htaccess.
  77
  78 11. If any issues were found during release in this document or in
  79     test-config-example.jam, commit those changes. The release need
  80     not be redone, but changes must be committed.
  81
  82 12. Set release date in changes.txt and commit.
  83