Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:31236 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 84443 invoked by uid 1010); 24 Jul 2007 12:36:16 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 84428 invoked from network); 24 Jul 2007 12:36:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Jul 2007 12:36:16 -0000 Authentication-Results: pb1.pair.com header.from=ilia@prohost.org; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=ilia@prohost.org; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain prohost.org from 64.233.166.183 cause and error) X-PHP-List-Original-Sender: ilia@prohost.org X-Host-Fingerprint: 64.233.166.183 py-out-1112.google.com Received: from [64.233.166.183] ([64.233.166.183:33162] helo=py-out-1112.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C7/B7-07574-E32F5A64 for ; Tue, 24 Jul 2007 08:36:16 -0400 Received: by py-out-1112.google.com with SMTP id f31so6024089pyh for ; Tue, 24 Jul 2007 05:36:12 -0700 (PDT) Received: by 10.35.78.9 with SMTP id f9mr7811997pyl.1185280571895; Tue, 24 Jul 2007 05:36:11 -0700 (PDT) Received: from ?192.168.1.223? ( [204.101.63.110]) by mx.google.com with ESMTPS id u62sm7577137pyb.2007.07.24.05.36.11 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 24 Jul 2007 05:36:11 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: 7bit Message-ID: <27429DED-5D5E-4D8E-AA21-EB2FF8E68E44@prohost.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: internals Mailing List Date: Tue, 24 Jul 2007 08:36:14 -0400 X-Mailer: Apple Mail (2.752.3) Subject: PHP 5.2.4RC1 Plan From: ilia@prohost.org (Ilia Alshanetsky) It has been a while since our last release and the ChangeLog has grown quite a bit, so I think it is time to start thinking about 5.2.4 release before the change set becomes unmanageable. To this effect I'd like to start the release cycle with RC1 planned for Thursday next week. Hopefully after the RC1 we can get to the final release within about a month's time. So, if you have any remaining major changes you want to apply, you have until Thursday, after RC1 only bug fixes and new test cases will be accepted. Ilia Alshanetsky