/*****************************************************************
- * Release Notes: SquirrelMail 1.2.0 *
- * The "And I Still Have Not Wrapped My Wife's Presents" Release *
- * aka the "Miriam Noel" Release *
- * December 25, 2001 *
+ * Release Notes: SquirrelMail 1.3.2 *
+ * The "Nut cracker" Release *
+ * 29 October 2002 *
*****************************************************************/
-After a long wait, SquirrelMail is finally making a new major stable
-series release. The past year has been ANYTHING but uneventful for
-the SquirrelMail Project. This year has seen two leadership changes,
-the release of the 1.0 series, the 1.1 development series, and now
-finally the much awaited 1.2.0 release.
-
In this edition of SquirrelMail Release Notes:
* All about this Release!!!
- * Reporting my favorite SquirrelMail 1.2.0 bug
- * Important Note about PHP 4.1.0
- * Where are we going from here?
-
+ * Major updates
+ * A note on solved bugs
+ * Reporting my favorite SquirrelMail 1.3 bug
+ * About our Release Aliases
All about this Release!!!
=========================
-Being one of the most popular webmail clients, the developers of
-SquirrelMail feel a huge desire and responsiblity to continue push
-the envelope and make SquirrelMail the best it can possibly be. You
-will not be disappointed with this release, as it is by far the most
-feature rich, and yet it is still the same sleak and unbloated and
-cuddly webmail application that we have all grown to love. Here is
-an uncomplete list of new features and enhancements since the last
-stable release.
-
- * Collapsable Folders - The folder list can be collapsed at any
- parent folder. This makes folder lists with large
- heirarchital structures much easier to manage and navigate.
- * The Paginator! - This enables quick access to any page in the
- message list by simply choosing the page number to view
- rather than tediously clicking "next" 50 times.
- * Hundreds of UI tweaks - The user interface has been given a
- facelift. The HTML has been largely overhauled, and while
- it still has the same general feel, it has been made more
- intuative.
- * Drafts - It is now possible to compose a message and save it to
- be sent at a later date with the drafts option.
- * New Options Page - The options page has been completely
- rewritten for several reasons, the main of which was to
- allow seamless integration of plugin options and to
- provide uniformity throughout the entire section.
- * Multiple Identities - It is now possible to create different
- identities (home, work, school) that can be chosen upon
- sending. Each identity can have its own email address,
- full name, and signature.
- * Reply Citations - Different types of citations are now possible
- when replying to messages.
- * Better Attachment Handling - The plugin, attachment_common, has
- been fully integrated into the core of SquirrelMail. This
- allows inline viewing of several different types of
- attachments.
- * Integration of Several Plugins - The following plugins have been
- put directly into the core. As a result, be sure not to
- install these as plugins, as the result may be (at best)
- unpredictable: attachment_common, paginator, priority
- printer_friendly, sqclock, xmailer.
- * Improved support for newer versions of PHP. Note that you may
- have trouble if you are running PHP version 4.0.100
- (commonly distributed with Debian 3.0).
- * Ablity to mark messages as read and unread from the message listing.
- * Alternating Colors - The message list now alternates row colors
- by default. This presents a much cleaner and easier to
- read interface to the user.
-
-Aside from these obvious front end features, there are hundreds of
-bugs that have been fixed, and much of the code has been optomized
-and/or rewritten. This stable release is far superior in all
-aspects to all previous versions of SquirrelMail.
-
- Home Page: http://www.squirrelmail.org/
- Download: http://www.squirrelmail.org/download.php
- ScreenShots: http://www.squirrelmail.org/screenshots.php
-
-
-Reporting my favorite SquirrelMail 1.2.0 bug
-============================================
-
-Of course, in the words of Linus Torvalds, this release is
-officially certified to be Bug-Free (tm).
-
-However, if for some reason some bugs manage to find their way to
-the surface, please report them at once (after all, they ARE
-uncertified bugs!!!) The PROPER place to report these bugs is the
-SquirrelMail Bug Tracker.
+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.
+
+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.
+
+Major updates
+==============
+
+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.
+
+
+A note on solved bugs
+=====================
+
+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 note on plugins
+=================
+
+There have been very severe 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
+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
+============================
+
+For a whole bunch of reasons, it is MANDATORY that you run conf.pl
+(and then save your configuration) from the config/ directory before
+using this release.
+
+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
+ * 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
+2) For your own pleasure and comfort:
+ turn of UID support in conf.pl, so you can continue to use 1.3.2
+
+
+Reporting my favorite SquirrelMail 1.3 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.
http://www.squirrelmail.org/bugs
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
+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.
+
-Important Note about PHP 4.1.0
-==============================
-
-First of all, let me say that you all HAVE been warned: the
-SquirrelMail Project Team is not supporting PHP 4.1.0 for the 1.2.0
-release. Basically, SquirrelMail was in the final death throws of
-this development series when the witty PHP folks decided to make the
-release of 4.1.0. Of course, we greatly appreciate their hard work! :)
-
-However, we were too close to the end of this whole thing to be able
-to spend the week or two EXTRA that it will take to get SquirrelMail
-1.2.0 PHP 4.1.0 ready. This will, on the bright side, be a major
-priority amongst the team in the immediate future. At first look, it
-seems that 4.1.0 support should just require a collection of
-relatively minor tweaks. You can expect 4.1.0 support within 2-3
-weeks, as a part of a later 1.2.X release.
-
-
-Where are we going from here?
-=============================
-
-After things cool down a bit and the smoke clears from 1.2.0,
-progress will begin on the Great SquirrelMail Rewrite, also known as
-the 1.3 development branch. This branch will eventually become the
-long talked about SquirrelMail 2.0. The major developmental emphasis
-for SquirrelMail 2.0 will be in making SquirrelMail more flexible
-and modular so that it might do a better job meeting the needs of
-our system administrators and end-users. We are greatly anticipating
-working in this area.
-
-At the same time, we will kick start the SquirrelMail Teams. For
-some time now, we have been planning a reorganization of the project
-into a variety of subteams. Each subteam will focus on a different
-aspect of SquirrelMail Project work. These teams will hopefully help
-keep the SquirrelMail project more on track and to provide some
-semblance of order. This project has grown so large in the past two
-years that an orderly structure is necessary if anything is to get
-done effectively. The teams (as planned) are as follows:
-
- Stable Series Team: Maintains the stable series
- Development Series Team: Works on the development series
- i18n Team: Handles i18n (internationalization) work
- Plugin Team: Manages the mass of plugins
- User Support Team: Helps users with their problems
- Documentation Team: Manages the documentation
- Evangelism Team: Spreads the good news of SquirrelMail
-
-Teams will be led by one or two SquirrelMail team members. And team
-members can participate in as many teams as he or she desires.
-
-For the next few weeks, the developers will be working on bugfixing
-and making the 1.2 series rock solid. After that, about mid January,
-focus will shift toward getting the teams in gear and starting work
-on the SquirrelMail 1.3 development series.
-
- Have a Merry Christmas!
Happy SquirrelMailing!
- The SquirrelMail Project Team
projects / squirrelmail.git / blobdiff