Getting ready for 1.4.0 RC1
[squirrelmail.git] / ReleaseNotes
... / ...
CommitLineData
1/*****************************************************************
2 * Release Notes: SquirrelMail 1.4.0 Release Candidate 1 *
3 * 31 December 2002 *
4 *****************************************************************/
5
6In this edition of SquirrelMail Release Notes:
7 * All about this Release!!!
8 * Major updates
9 * A note on plugins
10 * Reporting my favorite SquirrelMail 1.3 bug
11 * About our Release Aliases
12
13All about this Release!!!
14=========================
15
16This is the first Release Candidate (RC) for the 1.4.x stable series.
17Please note that this release is not yet labeled STABLE officially.
18
19However, we've been running this on a number of systems and a variety
20of configs and we think it's worthy of the "stable"-title. Before we
21can call it stable we want to test it on as many systems as possible
22to iron out the last issues.
23
24So download it! Install it, and try to break it! We are hungry for any
25bug report you send.
26
27
28Major updates
29==============
30
31The 1.4.0 series (as a result of 1.3 devel series) brings:
32
33* A complete rewrite of the way we send mail (Deliver-class),
34 and of the way we parse mail (MIME-bodystructure parsing).
35 This makes SquirrelMail more reliable and more efficient
36 at the same time!
37* Support for IMAP UID which makes SquirrelMail more reliable.
38* Optimizations to code and the number of IMAP calls.
39* Support for a wider range of authentication mechanisms.
40* Lots of bugfixes and a couple of UI-tweaks.
41
42
43
44A note on plugins
45=================
46
47There have been very severe architecture improvements. Lots of plugins
48have not yet been adapted to this. Plugins which are distributed with
49this release (eg. in the same .tar.gz file) may work. Plugins not
50distributed with this plugin most probably WILL NOT WORK.
51
52So if you have ANY problem at all, first try turning off all plugins.
53
54
55A note on your configuration
56============================
57
58For a whole bunch of reasons, it is MANDATORY that you run conf.pl
59(and then save your configuration) from the config/ directory before
60using this release.
61
62If you have problems with UID support, please do these 2 things:
63
641) For our comfort and the prosper of SquirrelMail:
65 send a bugreport with this information
66 * IMAP server type + version
67 * Whether you use server-side sorting
68 * Whether you use thread sorting
69 * The value of "sort" (as in conf.pl)
70 bugs can be submitted at: http://www.squirrelmail.org/bugs
712) For your own pleasure and comfort:
72 turn of UID support in conf.pl, so you can continue to use 1.4.0
73
74
75Reporting my favorite SquirrelMail 1.4 bug
76==========================================
77
78This RC is meant to catch the last bugs. So we need you to submit
79any bug you come across! Also, please mention that the bug is in
80this 1.4.0 RC1 release.
81
82 http://www.squirrelmail.org/bugs
83
84Thank you for your cooperation in that issue. That helps us to make
85sure that nothing slips through the cracks. Also, it would help if
86people would check existing tracker items for a bug before reporting
87it again. This would help to eliminate duplicate reports, and
88increase the time we can spend CODING by DECREASING the time we
89spend sorting through bug reports. And remember, check not only OPEN
90bug reports, but also closed ones as a bug that you report MAY have
91been fixed in CVS already.
92
93In case you want to join us on coding SquirrelMail, or have other
94things to share with the developers, join the development mailinglist:
95
96 squirrelmail-devel@lists.sourceforge.net
97
98
99 Happy SquirrelMailing!
100 - The SquirrelMail Project Team