| | 1 | /***************************************************************** |
| | 2 | * Release Notes: SquirrelMail 1.4.0 Release Candidate 2a * |
| | 3 | * 24 January 2002 * |
| | 4 | *****************************************************************/ |
| | 5 | |
| | 6 | In this edition of SquirrelMail Release Notes: |
| | 7 | * All about this Release!!! |
| | 8 | * Major updates |
| | 9 | * A note on plugins |
| | 10 | * Reporting my favorite SquirrelMail 1.4 bug |
| | 11 | |
| | 12 | All about this Release!!! |
| | 13 | ========================= |
| | 14 | |
| | 15 | This is the second and hopefully last Release Candidate (RC) for the |
| | 16 | 1.4.x stable series. Please note that this release is not yet labeled |
| | 17 | STABLE officially. |
| | 18 | |
| | 19 | It is labeled RC 2a because RC 2 was released but pulled back soon |
| | 20 | after because a serious bug was found that needed to be fixed. Thanks |
| | 21 | to Jason Munro for discovering this bug. |
| | 22 | |
| | 23 | However, we've been running this on a number of systems and a variety |
| | 24 | of configs and we think it's worthy of the "stable"-title. Before we |
| | 25 | can call it stable we want to test it on as many systems as possible |
| | 26 | to iron out the last issues. |
| | 27 | |
| | 28 | In response to RC1, quite some issues were reported AND fixed! We now |
| | 29 | hope that SquirrelMail is really ready to be called STABLE. We need you |
| | 30 | to verify that this is true! |
| | 31 | |
| | 32 | So download it! Install it, and try to break it! We are hungry for any |
| | 33 | bug report you send. Even the smallest issue deserves to be fixed. |
| | 34 | |
| | 35 | |
| | 36 | Major updates |
| | 37 | ============== |
| | 38 | |
| | 39 | The 1.4.0 series (as a result of 1.3 devel series) brings: |
| | 40 | |
| | 41 | * A complete rewrite of the way we send mail (Deliver-class), |
| | 42 | and of the way we parse mail (MIME-bodystructure parsing). |
| | 43 | This makes SquirrelMail more reliable and more efficient |
| | 44 | at the same time! |
| | 45 | * Support for IMAP UID which makes SquirrelMail more reliable. |
| | 46 | * Optimizations to code and the number of IMAP calls. |
| | 47 | * Support for a wider range of authentication mechanisms. |
| | 48 | * Lots of bugfixes and a couple of UI-tweaks. |
| | 49 | |
| | 50 | |
| | 51 | A note on plugins |
| | 52 | ================= |
| | 53 | |
| | 54 | There have been major plugin architecture improvements. Lots of plugins |
| | 55 | have not yet been adapted to this. Plugins which are distributed with |
| | 56 | this release (eg. in the same .tar.gz file) should work. Plugins not |
| | 57 | distributed with this plugin most probably WILL NOT WORK. |
| | 58 | |
| | 59 | So if you have ANY problem at all, first try turning off all plugins. |
| | 60 | |
| | 61 | |
| | 62 | A note on your configuration |
| | 63 | ============================ |
| | 64 | |
| | 65 | For a whole bunch of reasons, it is MANDATORY that you run conf.pl |
| | 66 | (and then save your configuration) from the config/ directory before |
| | 67 | using this release. |
| | 68 | |
| | 69 | If you have problems with UID support, please do these 2 things: |
| | 70 | |
| | 71 | 1) For our comfort and the prosperity of SquirrelMail, send a bug |
| | 72 | report with this information: |
| | 73 | * IMAP server type + version |
| | 74 | * Whether you use server-side sorting |
| | 75 | * Whether you use thread sorting |
| | 76 | * The value of "sort" (as in conf.pl) |
| | 77 | Bugs can be submitted at: http://www.squirrelmail.org/bugs |
| | 78 | |
| | 79 | 2) For your own pleasure and comfort: |
| | 80 | Turn off UID support in conf.pl, so you can continue to use 1.4.0 |
| | 81 | while the developers look at your report. |
| | 82 | |
| | 83 | |
| | 84 | Reporting my favorite SquirrelMail 1.4 bug |
| | 85 | ========================================== |
| | 86 | |
| | 87 | This RC is meant to catch the last bugs. So we need you to submit |
| | 88 | any bug you come across! Also, please mention that the bug is in |
| | 89 | this 1.4.0 RC2 release. |
| | 90 | |
| | 91 | http://www.squirrelmail.org/bugs |
| | 92 | |
| | 93 | Thanks for your cooperation with this. That helps us to make |
| | 94 | sure nothing slips through the cracks. Also, it would help if |
| | 95 | people would check existing tracker items for a bug before reporting |
| | 96 | it again. This would help to eliminate duplicate reports, and |
| | 97 | increase the time we can spend CODING by DECREASING the time we |
| | 98 | spend sorting through bug reports. And remember, check not only OPEN |
| | 99 | bug reports, but also closed ones as a bug that you report MAY have |
| | 100 | been fixed in CVS already. |
| | 101 | |
| | 102 | If you want to join us in coding SquirrelMail, or have other |
| | 103 | things to share with the developers, join the development mailinglist: |
| | 104 | |
| | 105 | squirrelmail-devel@lists.sourceforge.net |
| | 106 | |
| | 107 | |
| | 108 | Happy SquirrelMailing! |
| | 109 | - The SquirrelMail Project Team |
projects / squirrelmail.git / blame_incremental