Moreso july is somewhat arbitrarily around the OSCON which is when we all happen to be in Portland. Its a good excuse for a summertime beer with friends. =)
Really, I like to think what we're doing is 'rolling releases' with one overarching goal and bunch of mini goals to get there. Do a little Google around on 'release train'. It what we've been doing though some might argue we haven't spent enough time 'hardening'. I'd disagree given our bugs are around things like 'need better docs' and not epic-fail-code-no-compile type business. *shrug Its what ubuntu, firefox, chrome and others do. I'm not saying do stuff b/c everyone else is; but its a far better model than 'release when its done' aka 'release every 2 years or so' or worse. Working on a blog post to describe my thoughts on the benefits vs the drawbacks of the approach. Rather than releasing too early, or too late, just release on a regular schedule. Thats the basic premise. On Wed, Mar 28, 2012 at 4:57 PM, Filip Maj <[email protected]> wrote: > > > On 3/28/12 4:35 PM, "Patrick Mueller" <[email protected]> wrote: > >>On Wed, Mar 28, 2012 at 19:17, Filip Maj <[email protected]> wrote: >> >>> One point release per month: 1.7 end of April, 1.8 end of May, 1.9 end >>>of >>> June, 2.0 end of July. Exactly one year after we released 1.0 (although >>> the math doesn't quite add up there :P) >> >> >>So the release schedule is based around astronomical units???? > > Arbitrary astronomical units, yes. > > I'm OK with lining it up with the lunar calendar if that's what you're > suggesting. > >> >>-- >>Patrick Mueller >>http://muellerware.org >
