Changes between Initial Version and Version 1 of ReleasePractices/HeadsUpMessages

Timestamp:

Oct 11, 2008, 1:38:42 PM (14 years ago)

Author:

Beman Dawes

Comment:

Initial commit

ReleasePractices/HeadsUpMessages

@@ +1 @@
+= Release ''Heads Up'' Messages =
+
+These are the boilerplate messages that are posted to the Boost developers list as various deadlines loom.
+
+== [n.nn.n] Open for merging ==
+
+To be posted at the beginning of each release cycle when branches/release opens for commits:
+
+{{{
+
+branches/release is open for merging all stable changes from trunk, including
+bug fixes and major upgrades to existing libraries. Breaking changes should be
+coordinated via the mailing list with the developers of the other libraries
+affected. New libraries may be added, but require permission of a release manager.
+
+In other words, except for new libraries, merging changes *does not* need
+permission from a release manager. I.e. just do it!
+
+Links relating to this release:
+
+* Google Calendar with the release schedule: <http://www.boost.org/testing/index.html>.
+
+* Release schedule explanation: <http://svn.boost.org/trac/boost/wiki/ReleaseSchedule>.
+
+* Release practices for developers: <http://svn.boost.org/trac/boost/wiki/ImprovingPractices>.
+
+--(Release manager's names here)
+
+}}}
+
+== [n.nn.n] Deadline for new libraries approaching ==
+
+To be posted one week before branches/release closes for new libraries:
+
+{{{
+
+One week from today branches/release will close for commits of new libraries.
+
+Blah, blah, blah...
+
+}}}
+
+
+== Etc ==