X-Git-Url: https://vcs.fsf.org/?p=squirrelmail.git;a=blobdiff_plain;f=ReleaseNotes;h=4332e9a5ae5616b6c7f4d0ee0b6bd45fa82a8afc;hp=46601d263f726ed08093d731dc984a3dcd0874c7;hb=1b9f3c04fb7c772eef3a946782c8b70c60f9891c;hpb=0fbbeed6e529bbf0c616cb60273940f7a03ea6ec diff --git a/ReleaseNotes b/ReleaseNotes index 46601d26..4332e9a5 100644 --- a/ReleaseNotes +++ b/ReleaseNotes @@ -1,96 +1,103 @@ /***************************************************************** - * Release Notes: SquirrelMail 1.2.2 * - * The "International" Release * - * 1 January 2002 * + * Release Notes: SquirrelMail 1.3.1 * + * The "Marc for President!" Release * + * 19 august 2002 * *****************************************************************/ - Note: Please see the ChangeLog for 1.2.0 and 1.2.1 bugs that have - been fixed in this 1.2.2 release. - -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 release. - In this edition of SquirrelMail Release Notes: * All about this Release!!! - * Reporting my favorite SquirrelMail 1.2 bug - * Important Note about PHP 4.1.0 - * Where are we going from here? + * Reporting my favorite SquirrelMail 1.3 bug + * Important Note about PHP 4.2.2 * 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 responsibility 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 sleek and unbloated and -cuddly webmail application that we have all grown to love. Here is -an incomplete list of new features and enhancements since the last -stable release. - - * Collapsible Folders - The folder list can be collapsed at any - parent folder. This makes folder lists with large - hierarchical 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 - face-lift. The HTML has been largely overhauled, and while - it still has the same general feel, it has been made more - intuitive. - * 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). - * Ability 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 optimized -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 bug -========================================== +This is the second 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.7 is a stable version, and 1.3.1 (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. + + +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 PHP 4.2.2 +=================== + +There are certain issues with PHP 4.2.2 and session handling that have +not yet been addresses in this release. So this release MAY NOT WORK +when you use PHP 4.2.2. These issues will be addressed to in +forthcoming 1.3.x releases. -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. +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.1 + + +A note on MIME +============== + +In case you stumble over a message of which something goes wrong with +MIME (it does not display some of its parts all right, etc. etc.), +please forward the message AS AN ATTACHMENT to +squirrelmail-devel@lists.sourceforge.net. However, AVOID +forwarding emails over 20k of size. Please not as well that messages +which are NOT forwarded AS AN ATTACHMENT are COMPLETEY USELESS for our +testing purposes. + + +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.1 release. http://www.squirrelmail.org/bugs @@ -103,78 +110,25 @@ spend sorting through bug reports. And remember, check not only OPEN 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 + -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 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, -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 sub-teams. Each sub-team 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 bug-fixing -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. - - -About our Release Aliases - by Paul Joseph Thompson +About our Release Aliases - By Wouter Teepe ========================= -I just really appreciated how Wouter took charge and got this wonderful -1.2.1 release ready for prime time. It was not very long after I made -the 1.2.0 release when someone had already discovered the bug that made -the folders page screwed up for Netscape 4.x users. After the long hours -I put in getting 1.2.1 out, Wouter's quick help was a lifesaver. +In the last months we have had our development team enlarged by, +amongst others, Marc. Marc has been one of the greatest contributors +to the stable series. After the release of 1.3.0, just 2 days ago, he +managed to fix many many small bugs that were found. Almost when +others (including myself) just thought "Huh, another release?" Marc +was working hard to improve all kind of things. All fixes in this +release (and possibly new bugs ;-)) are due to his hard work. -I also want to thank Dave Huang for supplying the patch to Wouter via -the development list that fixed this icky bug. Thanks, Dave. Much -appreciation! +Keep up the good work, Marc! -See http://www.squirrelmail.org/wiki/SquirrelRelease for more details. - Have a Merry Christmas! Happy SquirrelMailing! - The SquirrelMail Project Team