X-Git-Url: https://vcs.fsf.org/?p=squirrelmail.git;a=blobdiff_plain;f=ReleaseNotes;h=09a230092088aa89cecf477429200b9ed3a8e266;hp=61d0387236c618b44605d216317196a0f7524cb3;hb=4e028e568b505e74ae4bae44513bfdca8c9f0123;hpb=c40982dab15bd66b667ed732180259d8162e2a9a diff --git a/ReleaseNotes b/ReleaseNotes index 61d03872..09a23009 100644 --- a/ReleaseNotes +++ b/ReleaseNotes @@ -1,99 +1,113 @@ /***************************************************************** - * 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.4.0 Release Candidate 2a * + * 24 January 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? - + * A note on PHP 4.3.x + * Major updates + * A note on plugins + * Reporting my favorite SquirrelMail 1.4 bug 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 second and hopefully last Release Candidate (RC) for the +1.4.x stable series. Please note that this release is not yet labeled +STABLE officially. + +It is labeled RC 2a because RC 2 was released but pulled back soon +after because a serious bug was found that needed to be fixed. Thanks +to Jason Munro for discovering this bug. + +However, we've been running this on a number of systems and a variety +of configs and we think it's worthy of the "stable"-title. Before we +can call it stable we want to test it on as many systems as possible +to iron out the last issues. + +In response to RC1, quite some issues were reported AND fixed! We now +hope that SquirrelMail is really ready to be called STABLE. We need you +to verify that this is true! + +So download it! Install it, and try to break it! We are hungry for any +bug report you send. Even the smallest issue deserves to be fixed. + +A note on PHP 4.3.x +=================== + +While the developers realize that PHP 4.3.x is the "latest and greatest" +version of PHP to be available, SquirrelMail has not been extensively +tested with it. There may be potential session issues with PHP 4.3.x, +and PHP by default has a session warning which will need to be disabled +if you wish to use it with SquirrelMail. + +Put simply: The SquirrelMail team does not recommend the use of +PHP 4.3.x with SquirrelMail at this time. + +SquirrelMail will put a large ugly warning about the use of PHP 4.3.x on +the login screen unless you add "$shootMyFootOff = true;" to +config/config_local.php, or downgrade PHP. + +Major updates +============== + +The 1.4.0 series (as a result of 1.3 devel series) brings: + +* A complete rewrite of the way we send mail (Deliver-class), + and of the way we parse mail (MIME-bodystructure parsing). + This makes SquirrelMail more reliable and more efficient + at the same time! +* Support for IMAP UID which makes SquirrelMail more reliable. +* Optimizations to code and the number of IMAP calls. +* Support for a wider range of authentication mechanisms. +* Lots of bugfixes and a couple of UI-tweaks. + + +A note on plugins +================= + +There have been major plugin 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) should 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 prosperity of SquirrelMail, send a bug + report 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 off UID support in conf.pl, so you can continue to use 1.4.0 + while the developers look at your report. + + +Reporting my favorite SquirrelMail 1.4 bug +========================================== + +This RC is meant to catch the last bugs. So we need you to submit +any bug you come across! Also, please mention that the bug is in +this 1.4.0 RC2 release. http://www.squirrelmail.org/bugs -Thank you for your cooperation in that issue. That helps us to make -sure that nothing slips through the cracks. Also, it would help if +Thanks for your cooperation with this. That helps us to make +sure nothing slips through the cracks. Also, it would help if people would check existing tracker items for a bug before reporting it again. This would help to eliminate duplicate reports, and increase the time we can spend CODING by DECREASING the time we @@ -101,62 +115,11 @@ 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. +If you want to join us in 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.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