On 10/29/2010 10:23 AM, Dean Michael Berris wrote:
On Sat, Oct 30, 2010 at 1:12 AM, Eric Niebler <eric@boostpro.com> wrote:
On 10/29/2010 5:03 AM, John Maddock wrote:
We really need to figure out a better way of dealing with this...
It currently requires a lot of discipline from each developer to make sure every change they apply to trunk also ends up in release. I wonder if commits to trunk to schedule a nag mail to be sent to the submitter a week later that says, "Did you check the tests? Did you merge to release?" Or open a track ticket that says, "merge changelist xxx to release."
How about if the release managers do it for the maintainers instead, and back out changes from the release branch in case things break from the test cycle?
The release managers need less to do, not more. Unless you're volunteering. :-) -- Eric Niebler BoostPro Computing http://www.boostpro.com