From: Todd Greer (todd.greer_at_[hidden])
Date: 2001-03-08 10:23:03
I'm starting to push the use of boost where I work, and I'm trying to
figure out how I should decide when to get updates, what versions I
will need to keep locally available even after more updates, and such
logistical issues. I would very much appreciate insight into how and
when new releases are made. Does a minor release promise no
incompatible changes? Is there a convention regarding version
numbers? Is anything allowed into boost_all.zip before it's
well-tested and stable? Is there some place I could have found this
information without needing to ask? I need to know these sorts of
things to control versions of boost used in our commercial products.
I suspect that this sort of information should be on the web site
somewhere, but I couldn't find any such information.
Boost has some great stuff, and I just need a little information
before I can bring it to our multitude of development efforts, some of
which share varying amounts of code, most of which have independant
Please feel free to throw in any random advice on this topic, as this
is my first attempt at doing this sort of thing.
Thank you in advance for this information, and thank you very much for
this fine set of libraries,
Todd Greer <todd.greer_at_[hidden]>
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk