1.3.0 is soon to be released, but before this happens, I need to make clear a few points I feel are important. The first is essential:
1) 1.3 is a development branch. We will both do bugfixes _and_ add/remove features, change existing code, break compatibility, add and remove classes and more between releases. There is no guarantee that anything in 1.3 is stable, especially not for production. 2) We will only release one tar.gz and one tar.bz2 for each release. In 1.3, bincimap.org will not make available binary packages nor src.rpm files, nor the (somewhat silly) tar.zip files. This is because I want to focus on writing code and documentation, rather than packaging. Third party packaging is of course completely fine. Snapshots will be available as before. 3) There will not be betas or release candidates for 1.3 until we prepare for 1.4. The final 1.3 releases before 1.4.0 is released will be tagged 1.3.x-rcN where N is the number of the release candidate. For 1.4 we most likely use 1.4.x-rcN for every release. Expect a high patch release version count (1.3.48 is not unrealistic). 4) Distributions currently pushing Binc IMAP 1.2 are discouraged from letting Binc IMAP 1.3 be an "upgrade" of Binc IMAP 1.2. This is because of all the porting problems that may follow, and we really don't want to deal with them until late 1.3, when 1.4 is being prepared. We do not want to ruin Binc IMAP's reputation as a rock solid server by letting users 'apt-get' themselves into a 1.3 nightmare ;-). Andy :-) -- Andreas Aardal Hanssen | http://www.andreas.hanssen.name/gpg Author of Binc IMAP | "It is better not to do something http://www.bincimap.org/ | than to do it poorly."
