On 04/08/2016 05:15 PM, Bron Gondwana via Cyrus-devel wrote:
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 long.
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!
Bron.
I don't know what effect this would have on imap, but I know that for
libsasl2, it would not be good to change the
release number for no reason. There are client applications out there
(openldap is the one I found) that check the
full release number and refuse to run if it is not identical to what it
was compiled with, and so changing a release number for no reason would
be very burdensome downstream.
Since I assume you're talking about imap, maybe it would not affect
anybody?
