[Dovecot] Is it 1.0 yet?
matthias.andree at gmx.de
Wed Feb 14 17:57:37 UTC 2007
Marc Perkel schrieb:
> OK - my last main bug was fixed a few releases ago. I know that there's
> no end to getting things right but there comes a point when you need to
> call it done. No one trusts a 1.0 to be perfect but Dovecot is already
> better that most 2.0 versions of other software.
> I vote (as if my vote counted) to call it done, declare victory, and
> move on to 1.01, 1.02 etc. No one is going to trus it till it gets to
> 1.02 so I say lets bless it and move on.
I'd urge Timo to leave it at "-rc" until the bug discovery (reporting)
rate has dropped considerably, until a stable set of documentation files
is ready to ship and only then call it stable.
Looking at the recent fixes, I think calling even rc22 "1.0" would be
There is a lot of things to do before it can become 1.0, not the least
is snapshotting the Wiki and polishing (in whichever order) a decent set
of documentation files. Deferring to the Wiki is definitely not the way
a "stable" software should be shipping its documentation. What if the
Wiki is down? Poking into the black... not a good idea.
There is absolutely no reason to rush 1.0 forward, because the label
bears no significance whatsoever about quality, and even less is the
code base as such impressed by such external "declaration of stability".
For those who want it, 1.0-rc* works well at many sites, and the
openSUSE build service has current candidates for public download (of
course, without warranties as to the usability or support, but they've
been quick to pick up new rc's).
My recent message (a few minutes ago, check the message date) in the
"resilience suggestion" thread has more points about this topic.
More information about the dovecot