Subject: Re: [boost] [release management] Draft policy for changes betweenbeta and release
From: Robert Ramey (ramey_at_[hidden])
Date: 2008-10-26 14:07:19
Phil Endecott wrote:
> Beman Dawes wrote:
>> what sort of QA problems should be fixed between the beta and final
>> releases * Minor code fixes.
>> * Questionable code fixes.
> One important factor not mentioned in the message is whether the fix
> is for a regression relative to the last release or is fixing a
> long-standing problem. From the point of view of an end-user, the
> difference between the new version "still not working" and "being more
> broken than the last" is significant. I would suggest that even quite
> large fixes should be accepted if they are fixing regressions, while
> even minor fixes that do not fix regressions should only be accepted
> if very obviously harmless.
Any library which has regressions as shown in trunk testing
should not be merged into the release ready branch. If it is
discovered that this has occurred, then the merge should
This policy is necessary for boost releases to guarentee
a strictly increasing level of quality.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk