Here is a suggestion for anyone who wants to do a "point release" or "hot fix" which applies to just a specific library. a) Start out with a release tree on your development system b) Switch the directories you want to change to "trunk". For date-time I would guess this boost/date_time and libs/date_time. c) Make your changes and test them on your machine. d) Commit changes, will go into the trunk e) Wait a week to verify that trunk tests are OK f) Switch back to release for your directories g) Merge changes into release -ready. h) Wait a little bit to watch tests on release - ready branch. i) NOW - make a hot fix release. choose one of the following: 1) make a zip file with just boost/date_time and libs/date_time directories. 2) make a unified diff between the above two directories 3) for those who suffer from release manager envy i) makean SVN branch date_time 1.37 hot fix from the 1.37 tag ii) merge in changes on these two directories from release-ready branch ii) invoke procedure to create release on this branch. Name your "thing" 1.37 + date_time hot fix. Robert Ramey David Abrahams wrote:
on Thu Oct 30 2008, "Beman Dawes" <bdawes-AT-acm.org> wrote:
Hum... So are you going to manage a point-release? That would change my thinking a bit.
No, I'm not committing to doing that. However, as you, Doug Gregor, and I agreed in San Francisco, there should be a branch of every release available for checking in critical bugfixes, so a user can get the updates by checking out from svn. It's not a point release, but it's far better than a collection of hotfix patches. Anyone who wants to selectively revert (or apply) fixes in the point release branch can do so easily with svn.