Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59632
Return-Path: <johannes@schlueters.de>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 45832 invoked from network); 10 Apr 2012 09:10:47 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 10 Apr 2012 09:10:47 -0000
Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown
Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
X-PHP-List-Original-Sender: johannes@schlueters.de
X-Host-Fingerprint: 217.114.211.66 config.schlueters.de  
Received: from [217.114.211.66] ([217.114.211.66:40334] helo=config.schlueters.de)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id C3/C0-41114-519F38F4 for <internals@lists.php.net>; Tue, 10 Apr 2012 05:10:46 -0400
Received: from [192.168.2.230] (unknown [93.104.14.82])
	(using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
	(Client did not present a certificate)
	by config.schlueters.de (Postfix) with ESMTPSA id 980F160D63;
	Tue, 10 Apr 2012 11:10:42 +0200 (CEST)
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: PHP Internals <internals@lists.php.net>
In-Reply-To: <4F82878A.6030609@sugarcrm.com>
References: <4F82878A.6030609@sugarcrm.com>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 10 Apr 2012 11:10:37 +0200
Message-ID: <1334049037.4609.14.camel@guybrush>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] release process with git
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Sun, 2012-04-08 at 23:54 -0700, Stas Malyshev wrote:
> Hi!
> 
> 5.4.1 will be the first release we're releasing using our new git setup.

As will 5.3.11.

> I would like to refine a process that we used to have for releases and
> make small tweaks hopefully to allow us more predictable release
> schedule and faster releases.
> What I am proposing is the following:
[...]

For 5.3.11+ my base assumption is that every bug in there exists for a
few years already (we don't add new features or such, do we? ;-) ).
Going from there I agree that fixes made during the release cycle can
easily wait for the next release. So the approach is fine.


For 5.3.11RC2 I'm currently looking at merging (cherry-picking)

  0f180a6 - Fixed bug in new stream_get_line() when using NUL as a delimiter.
    (This is a regression from 5.3.10)
  9bf8cd4 - Fixed bug #61650 (ini parser crashes when using ${xxxx} ini variables (without apache2))
    (Crash fix)
  ca58cd0 - Cherry-pick 4cc74767  Headers: forbid \r and \n also after \0, allow CRLF followed by HT or SP and forbid \0. See bug #60227.
    (Security related)
  55a6f3a - - update to openssl 0.9.8u
    (Readme change for Win distribution, no code change)
  0e53ac4 - - Updated to version 2012.3 (2012c)
    (current timezone data)
  8449e0c - Fixed bug #60718 Complie problem with libpq (PostgreSQL 7.3 or less)
     (compilation issue)

johannes