I never spoke about random immediate releases. All I said is that we should branch early, then give some time for people before the RC is cut. Branching early, I think, puts less risk that something random will get in. If you need to port something to the branch, you know it's the release branch. Maybe you'd decide not to do it and let it bake in 4x a while longer.
And maybe this is all just bullshit philosophy, I don't know. I do think that we're spending too much time on these silly arguments. We've never had two releases in a week's difference, there's no point threatening to do it. Plus, if it will happen, I'd probably vote for it too. And this time Adrien already said he won't be able to work on it until next Wednesday. So what are we arguing about? Rules? Principles? As far as I'm concerned, it should be the RM decision. Maybe he has time now but won't in a week? Fine, then another RM can come a week later and do another release... that's fine too. Shai On Sep 12, 2013 6:53 PM, "Mark Miller" <markrmil...@gmail.com> wrote: > > On Sep 12, 2013, at 11:45 AM, Robert Muir <rcm...@gmail.com> wrote: > > > I guess its ok that we disagree: fortunately you cannot veto releases, > > so its up to the individual release manager. > > > > I can throw up a RC right now and if 2 other people think its ok, its > > out the door. > > > > If i start to see the release process dragging ass for weeks and > > taking forever I might do such a thing. its just a few unix comands > > and an email. > > > > Your right - it only takes 3 PMC members to get a no warning release out > the door. > > However, fighting with the rules is fairly anti productive. > > Yes, a group could start doing random releases with no warning. > > Another group could start doing releases a week or two after those - > taking their time to wrap some things up first. > > Another guy could say, I'm going to start doing a release the last day of > every month, and then you will always be able to plan and we can work > together. > > Yes, if we can't get consensus, we can fall back to nuclear rule fallout. > > It seems more productive to simply give a weeks notice. > > If you are frustrated that a release has taken a long time and you want to > put up an RC? More power to you. That's not a random, no warning release. > I'd just as likely vote for it. > > - Mark > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >
