On Mon, 2007-01-22 at 12:34 -0500, Todd Vierling wrote:
From what I can see, dovecot could have released a 1.0 two or three RCs ago and released bugfixes via a 1.0.1, 1.0.2, etc. branch, with new development in a 1.1-beta line. Timo, we believe in your code... it works... so *please* slap a real release number on it, and we can finally convince others that it's time to switch. :)
I know the naming for Dovecot has sucked for years, but I haven't really seen any better ways to do it. I made the mistake in releasing v0.90 way too early.
Most of the new features in 1.0 RCs have been either trivial enough not to cause any destabilization or they've been implemented completely in plugins. Some of them have been paid for, and since they were done anyway I thought I might as well put them into RCs than maintain a list of patches that I have to keep updated constantly.
And sure, I suppose I could have just released v1.0 months ago, but I don't think it would have really changed anything else except to make more people try Dovecot, and possibly make them disappointed when they find bugs in what is supposed to be stable release.
I've for a long time thought that I'll release v1.0 once several weeks have passed and I haven't heard of any problems relating to index files and other such somewhat common random problems. I thought RC18 was supposed to fix all of them, but looks like there are again two more problems that more than one people are seeing.. I'd hate to release v1.0 and include in known bugs list things like "randomly crashes" and "randomly logs errors".
And 1.1-beta line already kind of exists in CVS HEAD. It has *huge* changes. I wish v1.0 were out just so I could start making v1.1 releases and get more people to test those changes.