Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:20930 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 95740 invoked by uid 1010); 1 Dec 2005 05:10:02 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 95724 invoked from network); 1 Dec 2005 05:10:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Dec 2005 05:10:02 -0000 X-Host-Fingerprint: 80.74.107.235 mail.zend.com Linux 2.5 (sometimes 2.4) (4) Received: from ([80.74.107.235:24293] helo=mail.zend.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id DB/01-14828-6A58E834 for ; Thu, 01 Dec 2005 00:10:01 -0500 Received: (qmail 23229 invoked from network); 1 Dec 2005 05:09:54 -0000 Received: from localhost (HELO ANDI-NOTEBOOK.zend.com) (127.0.0.1) by localhost with SMTP; 1 Dec 2005 05:09:54 -0000 Message-ID: <7.0.0.16.2.20051130210828.03f28ec0@zend.com> X-Mailer: QUALCOMM Windows Eudora Version 7.0.0.16 Date: Wed, 30 Nov 2005 21:09:51 -0800 To: Ilia Alshanetsky ,internals@lists.php.net In-Reply-To: <438E77BA.8060509@prohost.org> References: <438E77BA.8060509@prohost.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: [PHP-DEV] PHP 5.1.2 Release Plan From: andi@zend.com (Andi Gutmans) Sounds like a good plan to me. Is our confidence level on xmlwriter high? Just asking as I'm not sure how broadly it's been used and if we expect the API to have limitations or require changing at some point. Thx Ilia! At 08:10 PM 11/30/2005, Ilia Alshanetsky wrote: >Here is a brief outline of how I see 5.1.2 release happening and what in >my opinion should be included in the release. This is very much an RFC >as far as the changes go, so feel free to comment. > >First the release plan, my idea is to allow minor features with >accompanying tests that do not introduce any BC issues or functionality >regressions till the 10th of December. At this point we would go into a >feature and major change lock down, till about 22nd of December when the >first RC will be made. Through out this time only bug fixes will be >allowed and on Jan. 5th RC2 will be released. From that point we would >go into the final release stage at which point nothing short of critical >bug fixes be allowed. Assuming a 1 week period without such fixes >passes, final release will be tagged, making the last RC essentially >that release. In the even critical issues are discovered, additional RCs >will be rolled. > >Date Summary: (not be confused with date extension ;-) ) > >Until Dec. 10, 2005: Minor features and bug fixes requiring major changes >Dec. 22, 2005: RC1 >Jan. 05, 2006: RC2 >Jan. 12, 2006: Final (pending critical issues since RC2) > >Planned Changes: > >* Resolve all currently opened Engine bugs, ideally 5.1.2 will be > released without any unresolved engine problems. >* Resolve all currently open PDO bugs. >* Enable xmlreader extension by default, as we do for all XML > extensions. >* Introduce hash extension via a symlink from pecl into core. > This extension introduces native implementation of common hash > algorithms with streams support, making it an excellent solution > for people requiring better hashing then provided by md5/sha1. > Merits of this extensions have been discussed on this list few > weeks ago, just scroll past the recent flame wars ;-) >* Introduce xmlwriter extension via a symlink from pecl into core and as > other XML extension enable it by default. >* Backport oci extension into 5.1, this is mostly for bug fixing > reasons, as the new code fixes over a dozen bug reports in that > extension. > >Ilia > >-- >PHP Internals - PHP Runtime Development Mailing List >To unsubscribe, visit: http://www.php.net/unsub.php