+1. Thinking early releases will yield higher quality confuses cause and effect. The organization Jim describes is the organization I joined over a decade ago, and still think the values he expresses are worth hanging onto today.
On Feb 11, 2014, at 9:37 AM, Jim Jagielski <j...@jagunet.com> wrote: > > On Feb 11, 2014, at 12:51 AM, Marvin Humphrey <mar...@rectangular.com> wrote: > >> On Mon, Feb 10, 2014 at 3:57 PM, Dave Fisher <dave2w...@comcast.net> wrote: >>> I have a real example where defined cadence is not as good as the Apache >>> Way. >> >> Apache policy does not forbid releasing on a predictable schedule. Projects >> are already free to release quarterly, monthly, or even weekly if they >> choose. >> > > That's right. There are lots of little phrases like "Release > Early and Often" which emphasize that. But one of the nice > things about Open Source projects is that, well, it's NOT > work, its NOT a job, and we can also balance having a known > and reliable release schedule with "We Won't Release Until > Its Ready". > > PMCs aren't factories, churning out releases and code like > widgets. We do that enough at our day-jobs. PMC and Apache > projects should be, IMO of course, considered more like > making a good wine or brewing a fine ale. It's a craft. > It's an art form. FOSS projects should be fun and safe > places where you can practice your craft. >
