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.
<quote who="Marc Perkel">> 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. > >+1 -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 824887 E ghenry at suretecsystems.com Open Source. Open Solutions(tm). http://www.suretecsystems.com/
On Feb 13, 2007, at 12:46 PM, Marc Perkel wrote:> 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. >Agreed.
On Tue, Feb 13, 2007 at 12:46:19PM -0800, Marc Perkel wrote:> 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 only wish that dovecot would be able to use LDAP with reconnecting/rebinding before each authentication request: as I've mailed before, this is an issue for us, other softwares seems to work (because they reconnects each time, like ldap auth of squid for example). Ok, this may be a bug of OpenLDAP, I know ... -- - G?bor
I agree with most of your email, but maybe asking for a 1.0 release or pushing Timo to release it, is not that healthy. The "when will be 1.0 released?" topic have been posted many times, and the common answer seems to be: "the rc works just fine but please let Timo decide when 1.0 will come out" If you need a proof that the rc is working fine, just point your boss to the release notes of RedHat Enterprise 5, it has rc7 on it ;) HTH Oliver Marc Perkel wrote:> 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. >-- Oliver Schulze L. | Get my e-mail after a captcha in: Asuncion - Paraguay | http://tinymailto.com/oliver
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 premature. 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. Best regards, Matthias Andree