On Mon, Feb 10, 2014 at 8:34 PM, Joseph Schaefer <[email protected]> wrote:
> All I'm looking for is some evidence that tweaking the nobs and dials on
> release process has been done successfully in a project that has values
> similar to Apache projects.
Jenkins has been discussed -- is its governance not close enough to our
values for your taste?
https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document
Two other projects spring to mind which have migrated from ad hoc to scheduled
releases...
Firefox (though the transition was bumpy at first):
https://wiki.mozilla.org/RapidRelease
Perl 5:
http://lwn.net/Articles/485569/
Perl 5 has come a long way in the last few years. Every month, a new
development release comes out, shepherded by a different release manager.
Once a year, a new major version is released. Releasing a new major
version is no longer a months-long ordeal. When the new release schedule
was first proposed, many of us wondered if such an ambitious plan could
work. Now, it almost seems routine.
Marvin Humphrey
