fsf changes, meant to be rebased on upstream
[squirrelmail.git] / doc / release_notes_archive / 1.3 / Notes-1.3.1.txt
b38c6286 1/*****************************************************************
2 * Release Notes: SquirrelMail 1.3.1 *
3 * The "Marc for President!" Release *
4 * 19 august 2002 *
5 *****************************************************************/
7In this edition of SquirrelMail Release Notes:
8 * All about this Release!!!
9 * Reporting my favorite SquirrelMail 1.3 bug
10 * Important Note about PHP 4.2.2
11 * About our Release Aliases
13All about this Release!!!
16This is the second release on our way to a new stable series.
17On our way to, that is, this is a development release, which is not
18intended for production servers. We feel that releasing development
19versions will help us making the to-be stable release more stable, and
20restricting the ability to test no longer to people who use CVS.
22So download it! Install it, and try to break it! We are hungry for any
23bug report you send. If stumbling over a bug is a true non-option,
24this release is not for you. In that case, download the stable version
25and enjoy that one.
27In general, we are planning to regularly release a 1.3.x version until
28it is stable enough to call her 1.4 or 2.0. While I'm at it, one
29comment on version numbers. Our version numbers take the form of A.B.C
30 A increases with time, but only very seldomly.
31 B if it is even (0, 2, 4 etc), it is a stable release
32 if it is odd (1, 3, 5 etc), it is a development release
33 C indicates small changes.
34Which is to say our version numbering system is the same as that of
35the linux kernel. So 1.2.7 is a stable version, and 1.3.1 (this one)
36is a development release.
38We are excited to bring you the fruits of a very good development
39series. Major rewrites of the back-end and the user interface have
40been happening since the 1.2 series.
43A note on plugins
46There have been very severe architecture improvements. Lots of plugins
47have not yet been adapted to this. Plugins which are distributed with
48this release (eg. in the same .tar.gz file) may work. Plugins not
49distributed with this plugin most probably WILL NOT WORK.
51So if you have ANY problem at all, first try turning off all plugins.
54A note on PHP 4.2.2
57There are certain issues with PHP 4.2.2 and session handling that have
58not yet been addresses in this release. So this release MAY NOT WORK
59when you use PHP 4.2.2. These issues will be addressed to in
60forthcoming 1.3.x releases.
63A note on your configuration
66For a whole bunch of reasons, it is MANDATORY that you run conf.pl
67(and then save your configuration) from the config/ directory before
68using this release.
70If you have problems with UID support, please do these 2 things:
721) For our comfort and the prosper of SquirrelMail:
73 send a bugreport with this information
74 * IMAP server type + version
75 * Whether you use server-side sorting
76 * Whether you use thread sorting
77 * The value of "sort" (as in conf.pl)
78 bugs can be submitted at: http://www.squirrelmail.org/bugs
792) For your own pleasure and comfort:
80 turn of UID support in conf.pl, so you can continue to use 1.3.1
83A note on MIME
86In case you stumble over a message of which something goes wrong with
87MIME (it does not display some of its parts all right, etc. etc.),
88please forward the message AS AN ATTACHMENT to
89squirrelmail-devel@lists.sourceforge.net. However, AVOID
90forwarding emails over 20k of size. Please not as well that messages
91which are NOT forwarded AS AN ATTACHMENT are COMPLETEY USELESS for our
92testing purposes.
95Reporting my favorite SquirrelMail 1.3 bug
98It is not unlikely you will experience some bugs while using this
99development version. Please submit these bugs. Also, please mention
100that the bug is in this 1.3.1 release.
102 http://www.squirrelmail.org/bugs
104Thank you for your cooperation in that issue. That helps us to make
105sure that nothing slips through the cracks. Also, it would help if
106people would check existing tracker items for a bug before reporting
107it again. This would help to eliminate duplicate reports, and
108increase the time we can spend CODING by DECREASING the time we
109spend sorting through bug reports. And remember, check not only OPEN
110bug reports, but also closed ones as a bug that you report MAY have
111been fixed in CVS already.
113In case you want to join us on coding SquirrelMail, or have other
114things to share with the developers, join the development mailinglist:
116 squirrelmail-devel@lists.sourceforge.net
119About our Release Aliases - By Wouter Teepe
122In the last months we have had our development team enlarged by,
123amongst others, Marc. Marc has been one of the greatest contributors
124to the stable series. After the release of 1.3.0, just 2 days ago, he
125managed to fix many many small bugs that were found. Almost when
126others (including myself) just thought "Huh, another release?" Marc
127was working hard to improve all kind of things. All fixes in this
128release (and possibly new bugs ;-)) are due to his hard work.
130Keep up the good work, Marc!
133 Happy SquirrelMailing!
134 - The SquirrelMail Project Team