"Beman Dawes" <bdawes@acm.org> writes:
"Simon Carter" <simon.carter@ttplabtech.com> wrote in message news:loom.20060511T171525-434@post.gmane.org...
Beman Dawes <bdawes <at> acm.org> writes:
The link is broken for me.
I don't mind how the release is managed so long as I can use some kind of numbering system to completely identify the version of boost I have. As a minimum the overall boost version number should be incremented everytime anything in the release branch changes.
I'm thinking of cases where I know my app worked with (say) boost 1_30_0 but not with 1_32_0 - I need to be able to go back to the earlier version without jumping through hoops to reconstruct the state of the release branch at a particular point in time.
Good point. I've added a note to that effect, and suggested a number scheme based on the current practice.
SVN tags each state of the repository with a sequential number, so even intermediate states can be identified with those. -- Dave Abrahams Boost Consulting www.boost-consulting.com