Notes-1.2.1.txt 8.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180
  1. /*****************************************************************
  2. * Release Notes: SquirrelMail 1.2.1 *
  3. * The "Wouter for President" Release *
  4. * 25 December 2001 *
  5. *****************************************************************/
  6. Note: Please see the ChangeLog for 1.2.0 bugs that have been
  7. fixed in this 1.2.1 release.
  8. After a long wait, SquirrelMail is finally making a new major stable
  9. series release. The past year has been ANYTHING but uneventful for
  10. the SquirrelMail Project. This year has seen two leadership changes,
  11. the release of the 1.0 series, the 1.1 development series, and now
  12. finally the much awaited 1.2 release.
  13. In this edition of SquirrelMail Release Notes:
  14. * All about this Release!!!
  15. * Reporting my favorite SquirrelMail 1.2 bug
  16. * Important Note about PHP 4.1.0
  17. * Where are we going from here?
  18. * About our Release Aliases
  19. All about this Release!!!
  20. =========================
  21. Being one of the most popular webmail clients, the developers of
  22. SquirrelMail feel a huge desire and responsibility to continue push
  23. the envelope and make SquirrelMail the best it can possibly be. You
  24. will not be disappointed with this release, as it is by far the most
  25. feature rich, and yet it is still the same sleek and unbloated and
  26. cuddly webmail application that we have all grown to love. Here is
  27. an incomplete list of new features and enhancements since the last
  28. stable release.
  29. * Collapsible Folders - The folder list can be collapsed at any
  30. parent folder. This makes folder lists with large
  31. hierarchical structures much easier to manage and navigate.
  32. * The Paginator! - This enables quick access to any page in the
  33. message list by simply choosing the page number to view
  34. rather than tediously clicking "next" 50 times.
  35. * Hundreds of UI tweaks - The user interface has been given a
  36. face-lift. The HTML has been largely overhauled, and while
  37. it still has the same general feel, it has been made more
  38. intuitive.
  39. * Drafts - It is now possible to compose a message and save it to
  40. be sent at a later date with the drafts option.
  41. * New Options Page - The options page has been completely
  42. rewritten for several reasons, the main of which was to
  43. allow seamless integration of plugin options and to
  44. provide uniformity throughout the entire section.
  45. * Multiple Identities - It is now possible to create different
  46. identities (home, work, school) that can be chosen upon
  47. sending. Each identity can have its own email address,
  48. full name, and signature.
  49. * Reply Citations - Different types of citations are now possible
  50. when replying to messages.
  51. * Better Attachment Handling - The plugin, attachment_common, has
  52. been fully integrated into the core of SquirrelMail. This
  53. allows inline viewing of several different types of
  54. attachments.
  55. * Integration of Several Plugins - The following plugins have been
  56. put directly into the core. As a result, be sure not to
  57. install these as plugins, as the result may be (at best)
  58. unpredictable: attachment_common, paginator, priority,
  59. printer_friendly, sqclock, xmailer.
  60. * Improved support for newer versions of PHP. Note that you may
  61. have trouble if you are running PHP version 4.0.100
  62. (commonly distributed with Debian 3.0).
  63. * Ability to mark messages as read and unread from the message listing.
  64. * Alternating Colors - The message list now alternates row colors
  65. by default. This presents a much cleaner and easier to
  66. read interface to the user.
  67. Aside from these obvious front end features, there are hundreds of
  68. bugs that have been fixed, and much of the code has been optimized
  69. and/or rewritten. This stable release is far superior in all
  70. aspects to all previous versions of SquirrelMail.
  71. Home Page: http://www.squirrelmail.org/
  72. Download: http://www.squirrelmail.org/download.php
  73. ScreenShots: http://www.squirrelmail.org/screenshots.php
  74. Reporting my favorite SquirrelMail 1.2 bug
  75. ==========================================
  76. Of course, in the words of Linus Torvalds, this release is officially
  77. certified to be Bug-Free (tm).
  78. However, if for some reason some bugs manage to find their way to the
  79. surface, please report them at once (after all, they ARE uncertified
  80. bugs!!!) The PROPER place to report these bugs is the SquirrelMail Bug
  81. Tracker.
  82. http://www.squirrelmail.org/bugs
  83. Thank you for your cooperation in that issue. That helps us to make
  84. sure that nothing slips through the cracks. Also, it would help if
  85. people would check existing tracker items for a bug before reporting
  86. it again. This would help to eliminate duplicate reports, and
  87. increase the time we can spend CODING by DECREASING the time we
  88. spend sorting through bug reports. And remember, check not only OPEN
  89. bug reports, but also closed ones as a bug that you report MAY have
  90. been fixed in CVS already.
  91. Important Note about PHP 4.1.0
  92. ==============================
  93. First of all, let me say that you all HAVE been warned: the
  94. SquirrelMail Project Team is not supporting PHP 4.1.0 for the 1.2.0
  95. release. Basically, SquirrelMail was in the final death throws of
  96. this development series when the witty PHP folks decided to make the
  97. release of 4.1.0. Of course, we greatly appreciate their hard work! :)
  98. However, we were too close to the end of this whole thing to be able
  99. to spend the week or two EXTRA that it will take to get SquirrelMail
  100. 1.2 PHP 4.1.0 ready. This will, on the bright side, be a major
  101. priority amongst the team in the immediate future. At first look, it
  102. seems that 4.1.0 support should just require a collection of
  103. relatively minor tweaks. You can expect 4.1.0 support within 2-3
  104. weeks, as a part of a later 1.2.X release.
  105. Where are we going from here?
  106. =============================
  107. After things cool down a bit and the smoke clears from 1.2,
  108. progress will begin on the Great SquirrelMail Rewrite, also known as
  109. the 1.3 development branch. This branch will eventually become the
  110. long talked about SquirrelMail 2.0. The major developmental emphasis
  111. for SquirrelMail 2.0 will be in making SquirrelMail more flexible
  112. and modular so that it might do a better job meeting the needs of
  113. our system administrators and end-users. We are greatly anticipating
  114. working in this area.
  115. At the same time, we will kick start the SquirrelMail Teams. For
  116. some time now, we have been planning a reorganization of the project
  117. into a variety of sub-teams. Each sub-team will focus on a different
  118. aspect of SquirrelMail Project work. These teams will hopefully help
  119. keep the SquirrelMail project more on track and to provide some
  120. semblance of order. This project has grown so large in the past two
  121. years that an orderly structure is necessary if anything is to get
  122. done effectively. The teams (as planned) are as follows:
  123. Stable Series Team: Maintains the stable series
  124. Development Series Team: Works on the development series
  125. i18n Team: Handles i18n (internationalization) work
  126. Plugin Team: Manages the mass of plugins
  127. User Support Team: Helps users with their problems
  128. Documentation Team: Manages the documentation
  129. Evangelism Team: Spreads the good news of SquirrelMail
  130. Teams will be led by one or two SquirrelMail team members. And team
  131. members can participate in as many teams as he or she desires.
  132. For the next few weeks, the developers will be working on bug-fixing
  133. and making the 1.2 series rock solid. After that, about mid January,
  134. focus will shift toward getting the teams in gear and starting work
  135. on the SquirrelMail 1.3 development series.
  136. About our Release Aliases - by Paul Joseph Thompson
  137. =========================
  138. I just really appreciated how Wouter took charge and got this wonderful
  139. 1.2.1 release ready for prime time. It was not very long after I made
  140. the 1.2.0 release when someone had already discovered the bug that made
  141. the folders page screwed up for Netscape 4.x users. After the long hours
  142. I put in getting 1.2.1 out, Wouter's quick help was a lifesaver.
  143. I also want to thank Dave Huang for supplying the patch to Wouter via
  144. the development list that fixed this icky bug. Thanks, Dave. Much
  145. appreciation!
  146. See http://www.squirrelmail.org/wiki/SquirrelRelease for more details.
  147. Have a Merry Christmas!
  148. Happy SquirrelMailing!
  149. - The SquirrelMail Project Team