| 1 | /***************************************************************** |
| 2 | * Release Notes: SquirrelMail 1.3.2 * |
| 3 | * The "Nut cracker" Release * |
| 4 | * 29 October 2002 * |
| 5 | *****************************************************************/ |
| 6 | |
| 7 | In this edition of SquirrelMail Release Notes: |
| 8 | * All about this Release!!! |
| 9 | * Major updates |
| 10 | * A note on solved bugs |
| 11 | * Reporting my favorite SquirrelMail 1.3 bug |
| 12 | * About our Release Aliases |
| 13 | |
| 14 | All about this Release!!! |
| 15 | ========================= |
| 16 | |
| 17 | This is the third release on our way to a new stable series. |
| 18 | On our way to, that is, this is a development release, which is not |
| 19 | intended for production servers. We feel that releasing development |
| 20 | versions will help us making the to-be stable release more stable, and |
| 21 | restricting the ability to test no longer to people who use CVS. |
| 22 | |
| 23 | So download it! Install it, and try to break it! We are hungry for any |
| 24 | bug report you send. If stumbling over a bug is a true non-option, |
| 25 | this release is not for you. In that case, download the stable version |
| 26 | and enjoy that one. |
| 27 | |
| 28 | In general, we are planning to regularly release a 1.3.x version until |
| 29 | it is stable enough to call her 1.4 or 2.0. While I'm at it, one |
| 30 | comment on version numbers. Our version numbers take the form of A.B.C |
| 31 | A increases with time, but only very seldomly. |
| 32 | B if it is even (0, 2, 4 etc), it is a stable release |
| 33 | if it is odd (1, 3, 5 etc), it is a development release |
| 34 | C indicates small changes. |
| 35 | Which is to say our version numbering system is the same as that of |
| 36 | the linux kernel. So 1.2.9 is a stable version, and 1.3.2 (this one) |
| 37 | is a development release. |
| 38 | |
| 39 | We are excited to bring you the fruits of a very good development |
| 40 | series. Major rewrites of the back-end and the user interface have |
| 41 | been happening since the 1.2 series. |
| 42 | |
| 43 | Major updates |
| 44 | ============== |
| 45 | |
| 46 | To summarize the major updates in the 1.3.2 release: |
| 47 | * The support of register globals = off |
| 48 | * A complete rewrite of the way we send mail (Deliver-class) |
| 49 | * Lot's of bugfixes. |
| 50 | |
| 51 | |
| 52 | A note on solved bugs |
| 53 | ===================== |
| 54 | |
| 55 | After the release of 1.3.0 and 1.3.1 we received lots of usefull bug-reports. |
| 56 | At this moment we can say that most issues are solved. |
| 57 | One of the biggest bug reporter was Cor Bosman from the dutch ISP XS4ALL. |
| 58 | They scheduled the use of SquirrelMail 1.3.2 because of it's UID support. |
| 59 | At this moment they are switched over to 1.3.2 CVS and it's running fine on |
| 60 | the production servers. The imap-server load was dropped significantly and |
| 61 | that's exactly what we tried to establish in the DEVEL branche. |
| 62 | |
| 63 | |
| 64 | A note on plugins |
| 65 | ================= |
| 66 | |
| 67 | There have been very severe architecture improvements. Lots of plugins |
| 68 | have not yet been adapted to this. Plugins which are distributed with |
| 69 | this release (eg. in the same .tar.gz file) may work. Plugins not |
| 70 | distributed with this plugin most probably WILL NOT WORK. |
| 71 | |
| 72 | So if you have ANY problem at all, first try turning off all plugins. |
| 73 | |
| 74 | A note on your configuration |
| 75 | ============================ |
| 76 | |
| 77 | For a whole bunch of reasons, it is MANDATORY that you run conf.pl |
| 78 | (and then save your configuration) from the config/ directory before |
| 79 | using this release. |
| 80 | |
| 81 | If you have problems with UID support, please do these 2 things: |
| 82 | |
| 83 | 1) For our comfort and the prosper of SquirrelMail: |
| 84 | send a bugreport with this information |
| 85 | * IMAP server type + version |
| 86 | * Whether you use server-side sorting |
| 87 | * Whether you use thread sorting |
| 88 | * The value of "sort" (as in conf.pl) |
| 89 | bugs can be submitted at: http://www.squirrelmail.org/bugs |
| 90 | 2) For your own pleasure and comfort: |
| 91 | turn of UID support in conf.pl, so you can continue to use 1.3.2 |
| 92 | |
| 93 | |
| 94 | Reporting my favorite SquirrelMail 1.3 bug |
| 95 | ========================================== |
| 96 | |
| 97 | It is not unlikely you will experience some bugs while using this |
| 98 | development version. Please submit these bugs. Also, please mention |
| 99 | that the bug is in this 1.3.2 release. |
| 100 | |
| 101 | http://www.squirrelmail.org/bugs |
| 102 | |
| 103 | Thank you for your cooperation in that issue. That helps us to make |
| 104 | sure that nothing slips through the cracks. Also, it would help if |
| 105 | people would check existing tracker items for a bug before reporting |
| 106 | it again. This would help to eliminate duplicate reports, and |
| 107 | increase the time we can spend CODING by DECREASING the time we |
| 108 | spend sorting through bug reports. And remember, check not only OPEN |
| 109 | bug reports, but also closed ones as a bug that you report MAY have |
| 110 | been fixed in CVS already. |
| 111 | |
| 112 | In case you want to join us on coding SquirrelMail, or have other |
| 113 | things to share with the developers, join the development mailinglist: |
| 114 | |
| 115 | squirrelmail-devel@lists.sourceforge.net |
| 116 | |
| 117 | |
| 118 | About our Release Aliases |
| 119 | ========================= |
| 120 | With the release of 1.3.2 we can say we realy cracked some nuts regarding |
| 121 | hard to solve issues. |
| 122 | Future devel versions will continue carrying "Nut" releasenames |
| 123 | to keep the squirrel satisfied. Since winter is coming we better hurry up |
| 124 | with new "Nut" releases. We don't want a death squirrel due to starvation. |
| 125 | So next time you see a squirrel feed him nuts, think about SquirrelMail and |
| 126 | a new friendship is born. |
| 127 | |
| 128 | |
| 129 | Happy SquirrelMailing! |
| 130 | - The SquirrelMail Project Team |