Shuffling release notes
[squirrelmail.git] / doc / release_notes_archive / 1.3 / Notes-1.3.0.txt
1 /*****************************************************************
2 * Release Notes: SquirrelMail 1.3.0 *
3 * The "Pasta" Release *
4 * 17 august 2002 *
5 *****************************************************************/
6
7 In 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
12
13 All about this Release!!!
14 =========================
15
16 This is the first release on our way to a new stable series.
17 On our way to, that is, this is a development release, which is not
18 intended for production servers. We feel that releasing development
19 versions will help us making the to-be stable release more stable, and
20 restricting the ability to test no longer to people who use CVS.
21
22 So download it! Install it, and try to break it! We are hungry for any
23 bug report you send. If stumbling over a bug is a true non-option,
24 this release is not for you. In that case, download the stable version
25 and enjoy that one.
26
27 In general, we are planning to regularly release a 1.3.x version until
28 it is stable enough to call her 1.4 or 2.0. While I'm at it, one
29 comment 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.
34 Which is to say our version numbering system is the same as that of
35 the linux kernel. So 1.2.7 is a stable version, and 1.3.0 (this one)
36 is a development release.
37
38 We are excited to bring you the first fruits of a very good
39 development series. Major rewrites of the back-end and the user
40 interface have been happening since the 1.2 series. These rewrites
41 have inspired me for the release alias (see down this document).
42
43
44 A note on plugins
45 =================
46
47 There have been very severe architecture improvements. Lots of plugins
48 have not yet been adapted to this. Plugins which are distributed with
49 this release (eg. in the same .tar.gz file) may work. Plugins not
50 distributed with this plugin most probably WILL NOT WORK.
51
52 So if you have ANY problem at all, first try turning off all plugins.
53
54
55 A note on PHP 4.2.2
56 ===================
57
58 There are certain issues with PHP 4.2.2 and session handling that have
59 not yet been addresses in this release. So this release MAY NOT WORK
60 when you use PHP 4.2.2. These issues will be addressed to in
61 forthcoming 1.3.x releases.
62
63
64 A note on your configuration
65 ============================
66
67 For a whole bunch of reasons, it is MANDATORY that you run conf.pl
68 (and then save your configuration) from the config/ directory before
69 using this release.
70
71 If you have problems with UID support, please do these 2 things:
72
73 1) For our comfort and the prosper of SquirrelMail:
74 send a bugreport with this information
75 * IMAP server type + version
76 * Whether you use server-side sorting
77 * Whether you use thread sorting
78 * The value of "sort" (as in conf.pl)
79 bugs can be submitted at: http://www.squirrelmail.org/bugs
80 2) For your own pleasure and comfort:
81 turn of UID support in conf.pl, so you can continue to use 1.3.0
82
83
84 A note on MIME
85 ==============
86
87 In case you stumble over a message of which something goes wrong with
88 MIME (it does not display some of its parts all right, etc. etc.),
89 please forward the message AS AN ATTACHMENT to
90 squirrelmail-devel@lists.sourceforge.net. However, AVOID
91 forwarding emails over 20k of size. Please not as well that messages
92 which are NOT forwarded AS AN ATTACHMENT are COMPLETEY USELESS for our
93 testing purposes.
94
95
96 Reporting my favorite SquirrelMail 1.3 bug
97 ==========================================
98
99 It is not unlikely you will experience some bugs while using this
100 development version. Please submit these bugs. Also, please mention
101 that the bug is in this 1.3.0 release.
102
103 http://www.squirrelmail.org/bugs
104
105 Thank you for your cooperation in that issue. That helps us to make
106 sure that nothing slips through the cracks. Also, it would help if
107 people would check existing tracker items for a bug before reporting
108 it again. This would help to eliminate duplicate reports, and
109 increase the time we can spend CODING by DECREASING the time we
110 spend sorting through bug reports. And remember, check not only OPEN
111 bug reports, but also closed ones as a bug that you report MAY have
112 been fixed in CVS already.
113
114 In case you want to join us on coding SquirrelMail, or have other
115 things to share with the developers, join the development mailinglist:
116
117 squirrelmail-devel@lists.sourceforge.net
118
119
120 About our Release Aliases - By Wouter Teepe
121 =========================
122
123 Pasta is, as we all know, a group of Italian dishes. As most of us
124 know, several types of pasta exist, two of which are:
125
126 * Spaghetti: Tastes good, but is very hard to untangle. Its structure
127 is unneccecarily complex, but it is relatively easy to cook.
128 * Lasagne: Tastes excellent, and its structure is very elegant: it is
129 layered. Cooking it takes quite a bit more patience and design.
130
131 I will not bore you with Italian cooking more except for this: The
132 difference between spaghetti and lasagne applies to SquirrelMail as
133 well. Where 1.2 is good, its inside is unneccecarily complex. Opposed
134 to this, 1.3 is quite well structured from the inside. Its potential
135 is true excellence. Its flavor is already excellent. Expect 1.4/2.0 to
136 be, well...
137
138 With the slicing up the internals of SquirrelMail, whole new
139 possibilities will emerge. Listen on the development mailinglist to
140 hear which!
141
142
143 Happy SquirrelMailing!
144 - The SquirrelMail Project Team