Yo, It's obvious I really screwed up on the delay for the 1.4.0 release. All I can really do at this point is to make it up to the community by not ever sucking like that again, or by hanging my hat and passing on.
It should be easy to stick to a schedule from now on. If I can't keep on it we'll sort out a rotation. 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). 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. 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. Thoughts? -Dormando
