Subject: Re: [boost] Breaking existing libraries
Date: 2008-11-21 03:57:53
Markus Werle escribiÃ³:
> But let us go back on the we-do-not-pay-for-it path:
> IMHO it is a severe error of your development process that you do not
> check your code with new versions of all compilers and all libraries on a
> *regular* basis. In management parlance: your risk management is defective.
> It always is a good idea to use the svn repo of boost and the beta version
> of the next compiler just to see the breaking changes early enough, which gives
> everyone plenty of time to react.
On this particular point, I find that beta periods usually gather very
feedback from actual users of the code, and it is later in time when people
begin to complain about breaking changes (I'm meaning unintentional breaking
changes here). Somehow the Boost *users* community seems not to be
very involved in the release process, and we should find ways to press
test betas more thouroughly than it's being done currently. Maybe we can
begin by proactively sending announce mails to the companies in the
"Who's using Boost" entry whenever a beta period begins; we'd need a
contacts list to do that.
JoaquÃn M LÃ³pez MuÃ±oz
TelefÃ³nica, InvestigaciÃ³n y Desarrollo
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk