Legacy code was probably wrong
[squirrelmail.git] / doc / release_notes_archive / 1.2 / Notes-1.2.3.txt
CommitLineData
7aa617a0 1/*****************************************************************
2 * Release Notes: SquirrelMail 1.2.3 *
3 * The "One-Eyed Programmer" Release *
4 * 21 January 2002 *
5 *****************************************************************/
6
7 Note: Please see the ChangeLog for 1.2.0, 1.2.1 and 1.2.2 bugs
8 that have been fixed in this 1.2.2 release.
9
10After a long wait, SquirrelMail is finally making a new major stable
11series release. The past year has been ANYTHING but uneventful for
12the SquirrelMail Project. This year has seen two leadership changes,
13the release of the 1.0 series, the 1.1 development series, and now
14finally the much awaited 1.2 release.
15
16In this edition of SquirrelMail Release Notes:
17 * All about this Release!!!
18 * Reporting my favorite SquirrelMail 1.2 bug
19 * Important Note about PHP 4.1.0
20 * Where are we going from here?
21 * About our Release Aliases
22
23All about this Release!!!
24=========================
25
26Being one of the most popular webmail clients, the developers of
27SquirrelMail feel a huge desire and responsibility to continue push
28the envelope and make SquirrelMail the best it can possibly be. You
29will not be disappointed with this release, as it is by far the most
30feature rich, and yet it is still the same sleek and unbloated and
31cuddly webmail application that we have all grown to love. Here is
32an incomplete list of new features and enhancements since the last
33stable release.
34
35 * Collapsible Folders - The folder list can be collapsed at any
36 parent folder. This makes folder lists with large
37 hierarchical structures much easier to manage and navigate.
38 * The Paginator! - This enables quick access to any page in the
39 message list by simply choosing the page number to view
40 rather than tediously clicking "next" 50 times.
41 * Hundreds of UI tweaks - The user interface has been given a
42 face-lift. The HTML has been largely overhauled, and while
43 it still has the same general feel, it has been made more
44 intuitive.
45 * Drafts - It is now possible to compose a message and save it to
46 be sent at a later date with the drafts option.
47 * New Options Page - The options page has been completely
48 rewritten for several reasons, the main of which was to
49 allow seamless integration of plugin options and to
50 provide uniformity throughout the entire section.
51 * Multiple Identities - It is now possible to create different
52 identities (home, work, school) that can be chosen upon
53 sending. Each identity can have its own email address,
54 full name, and signature.
55 * Reply Citations - Different types of citations are now possible
56 when replying to messages.
57 * Better Attachment Handling - The plugin, attachment_common, has
58 been fully integrated into the core of SquirrelMail. This
59 allows inline viewing of several different types of
60 attachments.
61 * Integration of Several Plugins - The following plugins have been
62 put directly into the core. As a result, be sure not to
63 install these as plugins, as the result may be (at best)
64 unpredictable: attachment_common, paginator, priority,
65 printer_friendly, sqclock, xmailer.
66 * Improved support for newer versions of PHP. Note that you may
67 have trouble if you are running PHP version 4.0.100
68 (commonly distributed with Debian 3.0).
69 * Ability to mark messages as read and unread from the message listing.
70 * Alternating Colors - The message list now alternates row colors
71 by default. This presents a much cleaner and easier to
72 read interface to the user.
73
74Aside from these obvious front end features, there are hundreds of
75bugs that have been fixed, and much of the code has been optimized
76and/or rewritten. This stable release is far superior in all
77aspects to all previous versions of SquirrelMail.
78
79 Home Page: http://www.squirrelmail.org/
80 Download: http://www.squirrelmail.org/download.php
81 ScreenShots: http://www.squirrelmail.org/screenshots.php
82
83
84Reporting my favorite SquirrelMail 1.2 bug
85==========================================
86
87Of course, in the words of Linus Torvalds, this release is officially
88certified to be Bug-Free (tm).
89
90However, if for some reason some bugs manage to find their way to the
91surface, please report them at once (after all, they ARE uncertified
92bugs!!!) The PROPER place to report these bugs is the SquirrelMail Bug
93Tracker.
94
95 http://www.squirrelmail.org/bugs
96
97Thank you for your cooperation in that issue. That helps us to make
98sure that nothing slips through the cracks. Also, it would help if
99people would check existing tracker items for a bug before reporting
100it again. This would help to eliminate duplicate reports, and
101increase the time we can spend CODING by DECREASING the time we
102spend sorting through bug reports. And remember, check not only OPEN
103bug reports, but also closed ones as a bug that you report MAY have
104been fixed in CVS already.
105
106
107Important Note about PHP 4.1.0
108==============================
109
110First of all, let me say that you all HAVE been warned: the
111SquirrelMail Project Team is not supporting PHP 4.1.0 for the 1.2.0
112release. Basically, SquirrelMail was in the final death throws of
113this development series when the witty PHP folks decided to make the
114release of 4.1.0. Of course, we greatly appreciate their hard work! :)
115
116However, we were too close to the end of this whole thing to be able
117to spend the week or two EXTRA that it will take to get SquirrelMail
1181.2 PHP 4.1.0 ready. This will, on the bright side, be a major
119priority amongst the team in the immediate future. At first look, it
120seems that 4.1.0 support should just require a collection of
121relatively minor tweaks. You can expect 4.1.0 support within 2-3
122weeks, as a part of a later 1.2.X release.
123
124
125Where are we going from here?
126=============================
127
128After things cool down a bit and the smoke clears from 1.2,
129progress will begin on the Great SquirrelMail Rewrite, also known as
130the 1.3 development branch. This branch will eventually become the
131long talked about SquirrelMail 2.0. The major developmental emphasis
132for SquirrelMail 2.0 will be in making SquirrelMail more flexible
133and modular so that it might do a better job meeting the needs of
134our system administrators and end-users. We are greatly anticipating
135working in this area.
136
137At the same time, we will kick start the SquirrelMail Teams. For
138some time now, we have been planning a reorganization of the project
139into a variety of sub-teams. Each sub-team will focus on a different
140aspect of SquirrelMail Project work. These teams will hopefully help
141keep the SquirrelMail project more on track and to provide some
142semblance of order. This project has grown so large in the past two
143years that an orderly structure is necessary if anything is to get
144done effectively. The teams (as planned) are as follows:
145
146 Stable Series Team: Maintains the stable series
147 Development Series Team: Works on the development series
148 i18n Team: Handles i18n (internationalization) work
149 Plugin Team: Manages the mass of plugins
150 User Support Team: Helps users with their problems
151 Documentation Team: Manages the documentation
152 Evangelism Team: Spreads the good news of SquirrelMail
153
154Teams will be led by one or two SquirrelMail team members. And team
155members can participate in as many teams as he or she desires.
156
157For the next few weeks, the developers will be working on bug-fixing
158and making the 1.2 series rock solid. After that, about mid January,
159focus will shift toward getting the teams in gear and starting work
160on the SquirrelMail 1.3 development series.
161
162
163About our Release Aliases - by Wouter Teepe
164=========================
165
166Philippe, one of our main developers has been having quite some trouble
167with the health of his eyes. Though luckily it is not of a permanent
168nature, it is terrible enough. Essentially he had only one eye
169available when he was squashing many of the bugs that are fixed in this
170release.
171
172However, more eyes have been helping in making this release
173possible. I'd also like to specially thank Bron Godwana, who traced a
174bug in the IMAP code - and fixed it.
175
176See http://www.squirrelmail.org/wiki/SquirrelRelease for more details.
177
178 Happy SquirrelMailing!
179 - The SquirrelMail Project Team