[PHP-DEV] PHP 5.4.1 RC1 Released

Hi!

We would like to announce the first RC of the 5.4.1 version. This is
mainly a bugfix release, including all fixes that did not make the
cut for 5.4.0 and new issues since then. Please test it and notify us of
any problems you may encounter.
The full list of the fixes is as always in the NEWS file.

You can download the packages from:

http://downloads.php.net/stas

The Windows team provides windows binaries for the release.
As always you find them at:

http://windows.php.net/qa/

This is also the first release we are making from our brand new Git
setup, please tell us if you notice any glitches. You can
read more about the Git migration here:
http://www.php.net/archive/2012.php#id2012-03-20-1

We plan the next RC for 5.4.1 in two weeks, on April 12th.

Regards,
Stas & David

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

On Fri, 30 Mar 2012 09:04:28 +0200, Stas Malyshev <[email protected]>
wrote:

> The full list of the fixes is as always in the NEWS file.
>

I'm afraid it isn't. You did not merge the changes from 5.3 NEWS to 5.4.

I know this is controversial and some people have been committing to both
5.3 and 5.4 NEWS files. However, we have clear guidance for this:

70 3. All news updates intended for public viewing, such as new
features,
71 bug fixes, improvements, etc., should go into the NEWS file of
the
72 *first* to be released version with the given change. In other
words
73 any NEWS file change only needs to done in one branch.

http://git.php.net/?p=php-src.git;a=blob;f=README.SVN-RULES;h=de9d27490aecee211c07b6f6ee861d52d9f74ea9;hb=babe3ee0d2ba4f6c919bbb6710f232e6ef91e6ac#l70

As far as I remember, this was observed in the 5.2 era.

I think it would make more sense to change this rule and update all NEWS
files for stable branches as it would alleviate the RMs from the work of
determining which of the changes were 5.3 only, but either way we ought to
stick to one uniform rule. The status quo (some people updating one NEWS
file, others updating both) is not very satisfactory.

--
Gustavo Lopes

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Hi!

> I know this is controversial and some people have been committing to both
> 5.3 and 5.4 NEWS files. However, we have clear guidance for this:

OK, we need to have specific policy on it, because I'm hearing people
having contradictory opinions on that.

> I think it would make more sense to change this rule and update all NEWS
> files for stable branches as it would alleviate the RMs from the work of
> determining which of the changes were 5.3 only, but either way we ought to
> stick to one uniform rule. The status quo (some people updating one NEWS
> file, others updating both) is not very satisfactory.

I know, I will update NEWS for final release, but I want to know what
policy we adopt - "lowest version" NEWS or "all stable branches" NEWS?

--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

On 3/30/12 12:52 AM, Stas Malyshev wrote:
> Hi!
>
>> I know this is controversial and some people have been committing to both
>> 5.3 and 5.4 NEWS files. However, we have clear guidance for this:
>
> OK, we need to have specific policy on it, because I'm hearing people
> having contradictory opinions on that.

Pre git, I would have strongly voted that when a fix was merged to a
branch then that branch's NEWS file should be updated. At release
time the NEWS file would be already be complete. Snapshots would also
be consistent between code & NEWS.

This process differs from the documented one. With the way our git
repo is configured, I don't know if this causes merging issues.

NB the wiki gives git settings for NEWS:

$ git config merge.NEWS.name "Keep the NEWS file"
$ git config merge.NEWS.driver 'touch %A'

Chris


--
Email: christopher.jones@oracle.com
Tel: +1 650 506 8630
Blog: http://blogs.oracle.com/opal/

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php