Re: release process

On Sat, 2 Mar 2002, Yasuo Ohgaki wrote: >Jani Taskinen wrote: >> Just a small addition to this: >> >> These people who take care of the 'main' release of the branch >> will also be responsible for possible minor releases for the same >> branch. (4.2.0 is the main release, 4.2.1 a minor one..) >> >> So nobody but the RM shall _NOT_ touch the branch. >> _Only_ RM does MFH or RBM will B. >> >> Developers should be aware of this and notify the RM/RBM whenever >> they fix some bug and think it should be included in a minor release. >> >> --Jani > >I don't have problem with that since I'm not RM :) > >However, it seems hard job for RM to check all commit & merge. That's where the thing called 'discussion' comes in. You can politely ASK whether your überleet patch can get into the release.. >Since RM must maintain release branch at least few monthes >after 4.2.0 is released. It seems current way is working well. >We may need some guideline for how we maintain release brach, >though. > >We can try ;) I'd love to quote something Yoda said to Luke about trying.. but can't remember how it exactly was..something about not trying but simply _doing_ stuff.. And you don't have to worry about this. Derick and I are the ones who will worry and handle it. Besides, the main goal is to get rid of these extremely long periods of time between releases. --Jani