Thanks for kicking off the discussion on this. dormando wrote:
I'd like to propose something mildly similar to the linux kernel schedule, but inverted a little: - 3 weeks after each new stable release, we release -rc1 for the next release. - New -rc's will be kicked out daily or bidaily if there are fixes. - After 1 week in RC, unless there are still bug reports coming in, stable is released. So we should have a good stable release roughly once per month. Exceptions can be made, as usual. Major bug finds, emergencies, of course warrant earlier releases. Cycles with large code changes all at once might warrant an earlier cut to -rc1 and a 2-3 week -rc cycle (still trying to round it out at a month overall).
It could be because my backlog of goals and ideas isn't as aggressive as others, but to me this looks great other than the frequency. It feels a bit too frequent to me, but I'm only one voice. It feels more like 6 weeks or so makes sense (unless there's a security issue to deal with of course). The linux kernel probably needs the frequency because of the larger number of things going in.
Development should stay the way it is. All of us making code changes should be cc'ing as much as possible to the mailing list. I've noticed some of this has dropped off a little in recent days, but it's easy to pick that back up again. I do realize it's "easier" for people to just "follow" us on github, but lets stay open for the sake of discussion.
+1 This could also head off duplication of work... or worse... work that is incompatible.
Since OSCON is coming up, I'd like to give an extra week for the first cycle. Tentative date for 1.4.1-rc1 will be july 30th, with the stable release of 1.4.1 being on august 6th.
Makes sense to me! - Matt
