/*****************************************************************
- * Release Notes: SquirrelMail 1.3.2 *
- * The "Nut cracker" Release *
- * 29 October 2002 *
+ * Release Notes: SquirrelMail 1.4.0 Release Candidate 2a *
+ * 24 January 2002 *
*****************************************************************/
In this edition of SquirrelMail Release Notes:
* All about this Release!!!
+ * A note on PHP 4.3.x
* Major updates
- * A note on solved bugs
- * Reporting my favorite SquirrelMail 1.3 bug
- * About our Release Aliases
+ * A note on plugins
+ * Reporting my favorite SquirrelMail 1.4 bug
All about this Release!!!
=========================
-This is the third release on our way to a new stable series.
-On our way to, that is, this is a development release, which is not
-intended for production servers. We feel that releasing development
-versions will help us making the to-be stable release more stable, and
-restricting the ability to test no longer to people who use CVS.
+This is the second and hopefully last Release Candidate (RC) for the
+1.4.x stable series. Please note that this release is not yet labeled
+STABLE officially.
+
+It is labeled RC 2a because RC 2 was released but pulled back soon
+after because a serious bug was found that needed to be fixed. Thanks
+to Jason Munro for discovering this bug.
+
+However, we've been running this on a number of systems and a variety
+of configs and we think it's worthy of the "stable"-title. Before we
+can call it stable we want to test it on as many systems as possible
+to iron out the last issues.
+
+In response to RC1, quite some issues were reported AND fixed! We now
+hope that SquirrelMail is really ready to be called STABLE. We need you
+to verify that this is true!
So download it! Install it, and try to break it! We are hungry for any
-bug report you send. If stumbling over a bug is a true non-option,
-this release is not for you. In that case, download the stable version
-and enjoy that one.
-
-In general, we are planning to regularly release a 1.3.x version until
-it is stable enough to call her 1.4 or 2.0. While I'm at it, one
-comment on version numbers. Our version numbers take the form of A.B.C
- A increases with time, but only very seldomly.
- B if it is even (0, 2, 4 etc), it is a stable release
- if it is odd (1, 3, 5 etc), it is a development release
- C indicates small changes.
-Which is to say our version numbering system is the same as that of
-the linux kernel. So 1.2.9 is a stable version, and 1.3.2 (this one)
-is a development release.
-
-We are excited to bring you the fruits of a very good development
-series. Major rewrites of the back-end and the user interface have
-been happening since the 1.2 series.
+bug report you send. Even the smallest issue deserves to be fixed.
-Major updates
-==============
+A note on PHP 4.3.x
+===================
+
+While the developers realize that PHP 4.3.x is the "latest and greatest"
+version of PHP to be available, SquirrelMail has not been extensively
+tested with it. There may be potential session issues with PHP 4.3.x,
+and PHP by default has a session warning which will need to be disabled
+if you wish to use it with SquirrelMail.
+
+Put simply: The SquirrelMail team does not recommend the use of
+PHP 4.3.x with SquirrelMail at this time.
-To summarize the major updates in the 1.3.2 release:
-* The support of register globals = off
-* A complete rewrite of the way we send mail (Deliver-class)
-* Lot's of bugfixes.
+SquirrelMail will put a large ugly warning about the use of PHP 4.3.x on
+the login screen unless you add "$shootMyFootOff = true;" to
+config/config_local.php, or downgrade PHP.
+Major updates
+==============
-A note on solved bugs
-=====================
+The 1.4.0 series (as a result of 1.3 devel series) brings:
-After the release of 1.3.0 and 1.3.1 we received lots of usefull bug-reports.
-At this moment we can say that most issues are solved.
-One of the biggest bug reporter was Cor Bosman from the dutch ISP XS4ALL.
-They scheduled the use of SquirrelMail 1.3.2 because of it's UID support.
-At this moment they are switched over to 1.3.2 CVS and it's running fine on
-the production servers. The imap-server load was dropped significantly and
-that's exactly what we tried to establish in the DEVEL branche.
+* A complete rewrite of the way we send mail (Deliver-class),
+ and of the way we parse mail (MIME-bodystructure parsing).
+ This makes SquirrelMail more reliable and more efficient
+ at the same time!
+* Support for IMAP UID which makes SquirrelMail more reliable.
+* Optimizations to code and the number of IMAP calls.
+* Support for a wider range of authentication mechanisms.
+* Lots of bugfixes and a couple of UI-tweaks.
A note on plugins
=================
-There have been very severe architecture improvements. Lots of plugins
+There have been major plugin architecture improvements. Lots of plugins
have not yet been adapted to this. Plugins which are distributed with
-this release (eg. in the same .tar.gz file) may work. Plugins not
+this release (eg. in the same .tar.gz file) should work. Plugins not
distributed with this plugin most probably WILL NOT WORK.
So if you have ANY problem at all, first try turning off all plugins.
+
A note on your configuration
============================
If you have problems with UID support, please do these 2 things:
-1) For our comfort and the prosper of SquirrelMail:
- send a bugreport with this information
+1) For our comfort and the prosperity of SquirrelMail, send a bug
+ report with this information:
* IMAP server type + version
* Whether you use server-side sorting
* Whether you use thread sorting
* The value of "sort" (as in conf.pl)
- bugs can be submitted at: http://www.squirrelmail.org/bugs
+ Bugs can be submitted at: http://www.squirrelmail.org/bugs
+
2) For your own pleasure and comfort:
- turn of UID support in conf.pl, so you can continue to use 1.3.2
+ Turn off UID support in conf.pl, so you can continue to use 1.4.0
+ while the developers look at your report.
-Reporting my favorite SquirrelMail 1.3 bug
+Reporting my favorite SquirrelMail 1.4 bug
==========================================
-It is not unlikely you will experience some bugs while using this
-development version. Please submit these bugs. Also, please mention
-that the bug is in this 1.3.2 release.
+This RC is meant to catch the last bugs. So we need you to submit
+any bug you come across! Also, please mention that the bug is in
+this 1.4.0 RC2 release.
http://www.squirrelmail.org/bugs
-Thank you for your cooperation in that issue. That helps us to make
-sure that nothing slips through the cracks. Also, it would help if
+Thanks for your cooperation with this. That helps us to make
+sure nothing slips through the cracks. Also, it would help if
people would check existing tracker items for a bug before reporting
it again. This would help to eliminate duplicate reports, and
increase the time we can spend CODING by DECREASING the time we
bug reports, but also closed ones as a bug that you report MAY have
been fixed in CVS already.
-In case you want to join us on coding SquirrelMail, or have other
+If you want to join us in coding SquirrelMail, or have other
things to share with the developers, join the development mailinglist:
squirrelmail-devel@lists.sourceforge.net
-About our Release Aliases
-=========================
-With the release of 1.3.2 we can say we realy cracked some nuts regarding
-hard to solve issues.
-Future devel versions will continue carrying "Nut" releasenames
-to keep the squirrel satisfied. Since winter is coming we better hurry up
-with new "Nut" releases. We don't want a death squirrel due to starvation.
-So next time you see a squirrel feed him nuts, think about SquirrelMail and
-a new friendship is born.
-
-
Happy SquirrelMailing!
- The SquirrelMail Project Team
projects / squirrelmail.git / blobdiff