[Dovecot] 1.0-test74

[Raymond Lillard]

Andrew Hutchings wrote:
> Timo Sirainen wrote:
> 
>> http://dovecot.org/test/
>>
>> Not much has happened, but the APPEND bugfix is important since it was 
>> broken in test73 (at least). Summer makes me tired and lazy. :(
> 
> 
> Damn it, I only install 73 this morning :)
> I wish I had the time to be lazy, I'm certainly tired.
> 
>> I've been trying to get keywords implemented in maildir. Hopefully 
>> works soon.. After that I'll create 1.0-stable2 (ugh. any other naming 
>> ideas?) branch of the code before merging the new master/config code.
> 
> 
> Keep stable as is and maybe do:
> 1.0-beta?
> 1.0-RC?
> 
> It seems there are only minor things wrong now that are getting fixed 
> pretty quick, I think you are well on the way to having a beta release 
> by now.

Software that has entered the "Beta" state is usually considered
to be "feature complete".  Features may change with experience in
Beta code, but significant feature enhancements or new features are
not allowed.  Dovecot is still missing a few major features as I
understand the roadmap.

I think "stable2 is fine, since stable is presently used.  I
personally would have used the term "alpha" instead of "stable",
but a precedent has been set.  I would suggest not changing it
now.  In keeping with the "Law of Least Astonishment", the naming
convention of releases can be regularized after the formal release
of dovecot-1.0.

No changes in software that has reached the RC "release candidate"
phase are allowed except to directly fix bugs.  Software that lacks
sufficient maturity to hold to this rule must not be designated
"rc".

Failure to exercise this discipline (or something similar to it)
results in frustrated/angry users and embarrassed developers.

Regards all,
Ray