ReleaseNotes

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