On Tue, Jul 26, 2011 at 10:13:00AM -0700, Jeremy Kemper wrote: > On Mon, Jul 25, 2011 at 5:15 PM, Aaron Patterson > <[email protected]> wrote: > > Hi folks, > > > > I want to talk about the release process. Specifically, I want to talk > > about > > how we can improve our release process. > > > > There are a couple things I want to see in our release process: > > > > 1) Regular, periodic releases. > > Deadlines help force the issue of what's in and out of a release, too. +1. > > I'm wary of putting too much importance/significance in the fixed > schedule itself, rather than the desired outcome: reasonably frequent > stable releases that are easy to upgrade to. I doubt this'll become an > issue.
Agreed. I really don't want hard deadlines so much as I want to set expectations with users. Maybe we can say something like "approximately once per month". We have to strike a good balance. If we release too frequently, people are annoyed, but upgrades should be easier. If we release too infrequently, releases are harder and upgrades are harder. I guess it's important to make the distinction between setting expectations with the community vs timeline. I don't think it really matters what the schedule is, as long as everyone knows. > > 2) Distributed responsibility > > Happy to step back in front of the bus on these. Releases are a pretty > tedious exercise. Yay! I'll do the next releases (all releases through 3.1.0 and 3.0.10) and document the process along the way. We can start handing releases around after that. -- Aaron Patterson http://tenderlovemaking.com/
pgp6zz5cUEOlu.pgp
Description: PGP signature
