Beman Dawes <bdawes <at> acm.org> writes:
>
>
http://mysite.verizon.net/beman/release_overview.html.
>
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.
_______________________________________________
Unsubscribe & other changes:
http://lists.boost.org/mailman/listinfo.cgi/boost
