|
- |
- Home | -Libraries | -People | -FAQ | -More | -
Introduction
-Pre-release activities
-CVS Branch for release
-CVS Release
-Distribution
Historically, items on this checklist were accomplished by scripts written -in Perl, Python, Bash, C++, and as Windows command files, or by point-and-click -on a FrontPage or other GUI based program. Long term the plan is to move as much -as possible of these to C++, as -the one language all Boost developers are comfortable with.
----
-- Verify root/index.htm Latest News entry has been made and reads well.
-
-- Verify root/libs/libraries.htm entry has been made, both in the - alphabetic list and in the category lists.
-
-- Verify the root/libs/xxx directory contains an index.htm or index.html - file; either the main docs or a redirection to the main docs. To do: - automate this.
-
-- Skim read the primary docs pages to make sure they meet Boost - requirements and guidelines. Don't leave this until too late; it has - turned up lots of issues in the past.
-
-- Generate the header dependency table and update the CVS. To do: - coordinate with John Maddock's new dependency tools.
-
merged_to_RC_n_n_n.RC_n_n_n.These procedures are given for a particular release manager's machine. The -plan is to replace them with more generic procedures over time.
-cd ...\boost_1_28_0 -tar -cf site.tar * -bzip2 -k site.tar - -dir site.tar.bz2 -pscp site.tar.bz2 beman_dawes@shell1.sourceforge.net:/home/groups/b/bo/boost/htdocs/ - -keep_idsn_awake in another window. - -c:\bgd\util\putty\plink.exe beman_dawes@shell.sourceforge.net -cd /home/groups/b/bo/boost/htdocs -pwd -ls -l site.tar.bz2 - -rm -fr boost -rm -fr doc -rm -fr libs -rm -fr more -rm -fr people -rm -fr status -rm -fr tools -bunzip2 -kc site.tar.bz2 | tar -x -ls -exit - -stop keep_isdn_awake-
Revised: -21 November, 2005
-© Copyright Beman Dawes 2001
- -Distributed under the Boost Software License, Version 1.0. (See accompanying -file LICENSE_1_0.txt or copy at -http://www.boost.org/LICENSE_1_0.txt)
- - - - diff --git a/release_procedures.htm b/release_procedures.htm deleted file mode 100644 index aefa80a..0000000 --- a/release_procedures.htm +++ /dev/null @@ -1,213 +0,0 @@ - - - - - - - - -|
- |
- Home | -Libraries | -People | -FAQ | -More | -
Introduction
-Procedure Overview
-Procedures for Developers
-Procedures for the Release Manager
-FAQ
-Acknowledgements
Each release of Boost software is overseen by a release manager, who -coordinates release activities via the Boost mailing list, as well as performing -the detailed procedures for the release.
-Boost developers assist the release manager by reviewing regression test -logs, and committing fixes to CVS.
----
-- Command Line CVS:
----
-- Fixed code is committed to main branch
-
-- Switch to the release candidate branch -
---cvs update -r RC_1_26_2- Merge changes in a trunk since previous merge to branch -
---cvs update -jmerged_to_RC_1_26_2 -jHEAD buggycode.hpp - --> RCS file: /cvsroot/boost/.../buggycode.hpp,v - --> retrieving revision 1.4 - --> retrieving revision 1.6 - --> Merging differences between 1.4 and 1.6 into buggycode.hpp-- Commit merged branch -
---cvs commit -m "Merged fix for problem xyz from trunk to branch" buggycode.hpp-- Go back to main trunk -
---cvs update -A-- Move tag to a new merged point -
---cvs tag -F -c merged_to_RC_1_28_2 buggycode.hpp-- Repeat as needed -
--
-- WinCVS:
----
-- After fixed code is committed to main branch, switch to the release - candidate branch:
-----Select file(s) if not already selected.
-Modify | Update selection... | - Update settings | Sticky options | Retrieve rev/tag/branch:
-RC_1_26_2| OK-
-- Merge changes from main trunk into the release candidate branch:
-----Modify | Update selection... | - Update settings | Merge options | Only this rev/tag:
-- merged_to_RC_1_26_2- | Plus with this rev/tag:HEAD| OK-
-- Commit merge results:
-----Modify | Commit... | Enter log message: ... | OK
--
-- Go back to main trunk:
-----Modify | Update selection... | Update settings | Reset any sticky - date/tag/-k options | OK
--
-- Tag as new merge point:
-----Modify | Create tag on selection... | Create tag settings | Enter the tag - name to create:
-merged_to_RC_1_26_2, Overwrite existing tags - with same name | OK.
At time of branch-for-release:
-merged_to_RC_n_n_n.RC_n_n_n.See Release Manager's Checklist for -full details.
-What is the purpose of the -merged_to_RC_n_n_n tag? This tag allows multiple merges from the -main trunk to the release candidate branch. Without it, merging an initial main -trunk fix into the release candidate branch would work, but merging a -second fix from main trunk to release candidate branch would result in a merge -conflict. Although this procedure seems convoluted, it works much better in -practice than several prior procedures we tried.
-This web page was written by Beman Dawes, with helpful suggestions from Dave -Abrahams and Steve Robbins. Jim Hyslop contributed the original CVS procedures. -Updated by Jeff Garland after 1.29 release based on list discussions.
-Revised: -02 October, 2003
- -© Copyright Beman Dawes 2002
- -Distributed under the Boost Software License, Version 1.0. (See -accompanying file LICENSE_1_0.txt or copy -at http://www.boost.org/LICENSE_1_0.txt)
- - - - \ No newline at end of file