PHP 5.3.1 RC 1

hi Johannes,

I do not have the chance to match this planning. I'll be back from
holidays on Monday and will work on some of the critical issues we
have to fix from Wednesday only. The initial idea was to do 5.3.1 in
September not in August. I wonder what's the reasons behind this
change (as it drastically changes the initial planing...)? Besides the
usual "we have many fixes, let do a release" :).

Besides that it would be nice to avoid to release two versions on the
same day, even for a RC. We already have limited QA resources, no need
to put more work on us :).

Cheers,

Pierre

2009/8/6 Johannes Schlüter johannes@php.net:

Hi,

following Ilia's notice I want to give a heads-up for 5.3.1 RC1, too. We
have quite many fixes in SVN and the packaging script was successful in
my test.

I want to try to keep it along the same schedule as Ilia with 5.2 so we
can keep commit limitations - in case we need them - as limited as
possible. This means:

 "The aim  is to have RC1 next week thursday and if all goes well a
 final release by the end of August."

The biggest item I want to see fixed is the Sparc memory alignment bug
(#48668) which currently gives lots of trouble when using PHP on SPARC,
David is working on that and hopes to get a fix till RC1 done.

Cheers,

Pierre

http://blog.thepimp.net | http://www.libgd.org

Johannes,

While I am a big believer in release quickly, release often, I think
there are still a fair number of important if not critical bugs and
regressions in 5.3 that should be addressed before 5.3.1 is released.

Hi,

following Ilia's notice I want to give a heads-up for 5.3.1 RC1,
too. We
have quite many fixes in SVN and the packaging script was successful
in
my test.

I want to try to keep it along the same schedule as Ilia with 5.2 so
we
can keep commit limitations - in case we need them - as limited as
possible. This means:

"The aim is to have RC1 next week thursday and if all goes well a
final release by the end of August."

The biggest item I want to see fixed is the Sparc memory alignment bug
(#48668) which currently gives lots of trouble when using PHP on
SPARC,
David is working on that and hopes to get a fix till RC1 done.

Jani and others pointed me this morning (Europe time) to a few other
bugs on IRC, if you see any critical issues please let me know.

Thanks,
johannes

P.S. What is the current proposed tagging strategy? One of the
proposals
in a thread about that was Creating a branch (cp in branches/), verify
it, converting to a tag (mv banches/... tags/) -- any experience
there?