Release once per month whether we need to or not
me at anatoli.ws
Sat Apr 9 02:03:41 EDT 2016
It would be great! Also it'll help a lot to have a roadmap with ETAs for
each stage with a feature set defined. We're very interested in v3.0 and at
this time we have no idea about its present and future.
[mailto:cyrus-devel-bounces+me=anatoli.ws at lists.andrew.cmu.edu] On Behalf Of
Bron Gondwana via Cyrus-devel
Sent: Friday, April 08, 2016 21:16
To: Cyrus Devel
Subject: Release once per month whether we need to or not
So we have a problem. Our releases are rare, massive (and hence major
changes!) and nobody knows how to do them reliably because it's been too
We're planning to release the next 3.0 beta and the next 2.5 stable on
Monday. After that I want us to commit to the following:
* release a beta at least once per month
* release a stable at least once every 3 months
If we've got no changes, well - it's just a new release number with no
changes - should be simple to cut! Or we could go pick a small bug from
bugzilla/phabricator, write a test, ship it.
This will give us an easier job of actually releasing. After all, practice
makes perfect, and we're far from perfect at releasing right now!
brong at fastmail.fm
More information about the Cyrus-devel