Chinthaka +1 for your comment. :) Eran Chinthaka wrote:
>Whilst agreeing with Dims, here are few more points. > >We always can branch after a release, as we *always* create a tag, just >before the release. But so far, I've never seen we releasing a quick fix >after a release, using branches, in Apache WS projects. So I don't think >we have a problem in that. > >Creating branches before the release : The code will be frozen for a >small number of days. Creating branch will help people to improve the >code during that time. But what who decides which improvement should go >only to the branch or to both? The committer or the release manager >(RM)? I hope its the RM. > >Then we are asking him to do more work in addition to that tons of work >he has while releasing. He has to carefully analyze, *each* commit done >to the branch. Just be a RM once, you will realize how difficult it is. > >We are talking about pausing the development for couple of days vs more >hazzle to the RM. Why can't we help him for the release by testing the >artifacts in the mean time :). > >BTW, the subject says this is a vote. But the vote has moved away from >the original proposal. Do we wanna start a new vote or forget this (;) )? > >-- Chinthaka > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
