Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:46703
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain m.gmane.org designates 80.91.229.12 as permitted sender)
To: internals@lists.php.net
Followup-To:  gmane.comp.php.devel
Date:  Wed, 13 Jan 2010 10:55:55 -0600
Lines: 54
Message-ID: <hiktul$10v$1@ger.gmane.org>
References:  <hiin70$8s6$1@ger.gmane.org> <1263391216.5932.78.camel@guybrush>
Mime-Version:  1.0
Content-Type:  text/plain; charset="UTF-8"
Content-Transfer-Encoding:  8Bit
Sender: news <news@ger.gmane.org>
Subject:  Re: [PHP-DEV]  5.3 release schedule and other bits
From: geissert@debian.org (Raphael Geissert)

Johannes Schlüter wrote:

> Hi,
> 
> On Tue, 2010-01-12 at 14:48 -0600, Raphael Geissert wrote:
>> Hello,
>> 
>> At Debian we are planning to include PHP 5.3 in Squeeze, the next stable
>> release. As such, I would like to know for example when we could expect
>> 5.3.2 and 5.3.3 to be released.
> 
> I hope that the new release branch mere-tracking-tool goes live today,
> so that the new experimental release branch based process works nicer,
> so 5.3.2RC2 will follow shortly after (either until tomorrow, which will
> be quite a rush, better tuesday next week) further progress then depends
> on feedback from testers, hopefully 5.3.2 will be out very late
> January/early February.
> for 5.3.3 it depends on security issues being reported, bug fixes going
> in, ... maybe 3 months after.

Ok, so it looks we will be releasing with 5.3.2 + any backported patch 
necessary to fix important or critical bugs. Thanks for the info.

> 
>> On a slightly different topic, I'd like to express that I would like to
>> improve the communication between us (the package maintainers) and you
>> (the upstream developers). As a first step I'll be trying to forward most
>> of our patches so that there's a minor divergence.
> 
> I think that's an important topic. And I think it would be good to
> improve communication with packagers to unify things that might be
> handled differently and prevent packagers from back-porting security
> fixes in a wrong way. I now that MySQL has a "packgers" list, maybe such
> a thing might be good for php, too. internals might sometimes be a bit
> crowded to follow ...
> 

Such kind of mailing list might be useful, yes. It would at least help give 
the impression that there's interest on improving the communication 
channels.
That said, I think reading and at times discussing stuff here will still be 
needed.
As for security patches, yes, it would help if for every issue there's a 
pointer to the commits fixing them. I recently started a discussion on oss-
sec about PHP's security policy, but haven't brought it up with the php 
security team yet.

I hope we can make a progress.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net