+
+Reporting my favorite SquirrelMail 1.2 bug
+==========================================
+
+Of course, in the words of Linus Torvalds, this release is officially
+certified to be Bug-Free (tm).
+
+However, if for some reason some bugs manage to find their way to the
+surface, please report them at once (after all, they ARE uncertified
+bugs!!!) The PROPER place to report these bugs is the SquirrelMail Bug
+Tracker.
+
+ http://www.squirrelmail.org/bugs
+
+Thank you for your cooperation in that issue. That helps us to make
+sure that nothing slips through the cracks. Also, it would help if
+people would check existing tracker items for a bug before reporting
+it again. This would help to eliminate duplicate reports, and
+increase the time we can spend CODING by DECREASING the time we
+spend sorting through bug reports. And remember, check not only OPEN
+bug reports, but also closed ones as a bug that you report MAY have
+been fixed in CVS already.
+
+
+Important Note about PHP 4.1.0
+==============================
+
+First of all, let me say that you all HAVE been warned: the
+SquirrelMail Project Team is not supporting PHP 4.1.0 for the 1.2.0
+release. Basically, SquirrelMail was in the final death throws of
+this development series when the witty PHP folks decided to make the
+release of 4.1.0. Of course, we greatly appreciate their hard work! :)
+
+However, we were too close to the end of this whole thing to be able
+to spend the week or two EXTRA that it will take to get SquirrelMail
+1.2 PHP 4.1.0 ready. This will, on the bright side, be a major
+priority amongst the team in the immediate future. At first look, it
+seems that 4.1.0 support should just require a collection of
+relatively minor tweaks. You can expect 4.1.0 support within 2-3
+weeks, as a part of a later 1.2.X release.
+
+
+Where are we going from here?
+=============================
+
+After things cool down a bit and the smoke clears from 1.2,
+progress will begin on the Great SquirrelMail Rewrite, also known as
+the 1.3 development branch. This branch will eventually become the
+long talked about SquirrelMail 2.0. The major developmental emphasis
+for SquirrelMail 2.0 will be in making SquirrelMail more flexible
+and modular so that it might do a better job meeting the needs of
+our system administrators and end-users. We are greatly anticipating
+working in this area.
+
+At the same time, we will kick start the SquirrelMail Teams. For
+some time now, we have been planning a reorganization of the project
+into a variety of sub-teams. Each sub-team will focus on a different
+aspect of SquirrelMail Project work. These teams will hopefully help
+keep the SquirrelMail project more on track and to provide some
+semblance of order. This project has grown so large in the past two
+years that an orderly structure is necessary if anything is to get
+done effectively. The teams (as planned) are as follows: