ReleaseNotes

   1 /*****************************************************************
   2  * Release Notes: SquirrelMail 1.3.1                             *
   3  * The "Marc for President!" Release                             *
   4  * 19 august 2002                                                *
   5  *****************************************************************/
   6
   7 In this edition of SquirrelMail Release Notes:
   8    * All about this Release!!!
   9    * Reporting my favorite SquirrelMail 1.3 bug
  10    * Important Note about PHP 4.2.2
  11    * About our Release Aliases
  12
  13 All about this Release!!!
  14 =========================
  15
  16 This is the second release on our way to a new stable series.
  17 On our way to, that is, this is a development release, which is not
  18 intended for production servers. We feel that releasing development
  19 versions will help us making the to-be stable release more stable, and
  20 restricting the ability to test no longer to people who use CVS.
  21
  22 So download it! Install it, and try to break it! We are hungry for any
  23 bug report you send. If stumbling over a bug is a true non-option,
  24 this release is not for you. In that case, download the stable version
  25 and enjoy that one.
  26
  27 In general, we are planning to regularly release a 1.3.x version until
  28 it is stable enough to call her 1.4 or 2.0. While I'm at it, one
  29 comment on version numbers. Our version numbers take the form of A.B.C
  30  A increases with time, but only very seldomly.
  31  B if it is even (0, 2, 4 etc), it is a stable release
  32    if it is odd (1, 3, 5 etc), it is a development release
  33  C indicates small changes.
  34 Which is to say our version numbering system is the same as that of
  35 the linux kernel. So 1.2.7 is a stable version, and 1.3.1 (this one)
  36 is a development release.
  37
  38 We are excited to bring you the fruits of a very good development
  39 series. Major rewrites of the back-end and the user interface have
  40 been happening since the 1.2 series.
  41
  42
  43 A note on plugins
  44 =================
  45
  46 There have been very severe architecture improvements. Lots of plugins
  47 have not yet been adapted to this. Plugins which are distributed with
  48 this release (eg. in the same .tar.gz file) may work. Plugins not
  49 distributed with this plugin most probably WILL NOT WORK.
  50
  51 So if you have ANY problem at all, first try turning off all plugins.
  52
  53
  54 A note on PHP 4.2.2
  55 ===================
  56
  57 There are certain issues with PHP 4.2.2 and session handling that have
  58 not yet been addresses in this release. So this release MAY NOT WORK
  59 when you use PHP 4.2.2. These issues will be addressed to in
  60 forthcoming 1.3.x releases.
  61
  62
  63 A note on your configuration
  64 ============================
  65
  66 For a whole bunch of reasons, it is MANDATORY that you run conf.pl
  67 (and then save your configuration) from the config/ directory before
  68 using this release.
  69
  70 If you have problems with UID support, please do these 2 things:
  71
  72 1) For our comfort and the prosper of SquirrelMail:
  73    send a bugreport with this information
  74      * IMAP server type + version
  75      * Whether you use server-side sorting
  76      * Whether you use thread sorting
  77      * The value of "sort" (as in conf.pl)
  78    bugs can be submitted at: http://www.squirrelmail.org/bugs
  79 2) For your own pleasure and comfort:
  80    turn of UID support in conf.pl, so you can continue to use 1.3.1
  81
  82
  83 A note on MIME
  84 ==============
  85
  86 In case you stumble over a message of which something goes wrong with
  87 MIME (it does not display some of its parts all right, etc. etc.),
  88 please forward the message AS AN ATTACHMENT to
  89 squirrelmail-devel@lists.sourceforge.net. However, AVOID
  90 forwarding emails over 20k of size. Please not as well that messages
  91 which are NOT forwarded AS AN ATTACHMENT are COMPLETEY USELESS for our
  92 testing purposes.
  93
  94
  95 Reporting my favorite SquirrelMail 1.3 bug
  96 ==========================================
  97
  98 It is not unlikely you will experience some bugs while using this
  99 development version. Please submit these bugs. Also, please mention
 100 that the bug is in this 1.3.1 release.
 101
 102    http://www.squirrelmail.org/bugs
 103
 104 Thank you for your cooperation in that issue. That helps us to make
 105 sure that nothing slips through the cracks. Also, it would help if
 106 people would check existing tracker items for a bug before reporting
 107 it again. This would help to eliminate duplicate reports, and
 108 increase the time we can spend CODING by DECREASING the time we
 109 spend sorting through bug reports. And remember, check not only OPEN
 110 bug reports, but also closed ones as a bug that you report MAY have
 111 been fixed in CVS already.
 112
 113 In case you want to join us on coding SquirrelMail, or have other
 114 things to share with the developers, join the development mailinglist:
 115
 116    squirrelmail-devel@lists.sourceforge.net
 117
 118
 119 About our Release Aliases - By Wouter Teepe
 120 =========================
 121
 122 In the last months we have had our development team enlarged by,
 123 amongst others, Marc. Marc has been one of the greatest contributors
 124 to the stable series. After the release of 1.3.0, just 2 days ago, he
 125 managed to fix many many small bugs that were found. Almost when
 126 others (including myself) just thought "Huh, another release?" Marc
 127 was working hard to improve all kind of things. All fixes in this
 128 release (and possibly new bugs ;-)) are due to his hard work.
 129
 130 Keep up the good work, Marc!
 131
 132
 133                   Happy SquirrelMailing!
 134                     - The SquirrelMail Project Team