
Bug reports from the beta are starting to surface on the user's list. Here is the procedure for dealing with them: * Apply the fix to the trunk. * Wait until enough regression tests have cycled to demonstrate that the fix worked and didn't break anything else. * Apply the fix to branches/release. * Keep an eye on the release test results to be sure there were no unintended consequences. In other words, there is no need to ask the release managers for permission to apply to branches/release as long as tests are clean. The whole point of doing a beta is to shake these user detected bugs out of the woodwork and apply the resulting fixes in time for the release. Thanks, --Beman

----- Original Message ----- From: "Beman Dawes" <bdawes@acm.org> To: "Boost Developers Mailing List" <boost@lists.boost.org> Sent: Friday, August 01, 2008 1:51 PM Subject: [boost] [1.36.0 beta] Bug fix procedures
In other words, there is no need to ask the release managers for permission to apply to branches/release as long as tests are clean. The whole point of doing a beta is to shake these user detected bugs out of the woodwork and apply the resulting fixes in time for the release.
Hi, When the bug is detected outside the regression tests, maybe a test should be added to check that the bug is no more present. Vicente

In other words, there is no need to ask the release managers for permission to apply to branches/release as long as tests are clean. The whole point of doing a beta is to shake these user detected bugs out of the woodwork and apply the resulting fixes in time for the release.
When the bug is detected outside the regression tests, maybe a test should be added to check that the bug is no more present.
That is normal good practice anyway: any bug should ideally be reproduced first, test added, and then fixed. Unfortunately that doesn't help if the problem is specific to a platform/compiler we don't have regression tests for :-( John.
participants (3)
-
Beman Dawes
-
John Maddock
-
vicente.botet