After a discussion between Andi and myself, with his blessing I am
assuming the 5.1 RM role. The passing along of the RM mantle will
hopefully permit us to revitalize the 5.1 release process and get this
thing outta the door.
So, here is the plan [tm] :-)
I would like to release RC2 within week, October 14th to be precise. I
anticipate this will NOT be a final RC, so please don't panic. I want
this to be solid pre-final that we can use to validate everything and if
all goes well, release 5.1 by the end of October.
To accomplish this your help is needed, not just the developers but
everyone. So, if you want a solid 5.1 release, now is the time to pitch in.
On the developer end I would like all committers to restrict their
patches to bug fixes and ONLY bug fixes as far as the 5.1 branch is
concerned. For large changes, please confirm the change with me first
before proceeding. As far as bugs go, we have about 120 open for 5.X
series, most of them are assigned. If any of them are yours, please see
if you can find the time in the very near future to look at them.
Aside from bug fixing, I'd like to ask everyone to download 5.1 from cvs
or snapshots (http://snaps.php.net) and run it. See what problems you
encounter and report them here. If this is not done, don't be surprised
to see your stuff not work with 5.1, you'll only have yourself to blame.
One of the very good ideas Andi had, which I wholly support is that we
need documentation on upgrading from 5.0 to 5.1, what changed, how to
work around it etc... If you aware of any BC breaks in 5.1, please
identify them here so that they can be put into usable documentation.
Date handling, this is a big one, probably responsible for the most
recent set of delays. If you have a specific problem (example test
case), let me know. I'll bug Derick until he fixes it ;-) Mind you, a
number of patches to the code have been applied to CVS in the last few
days, so be sure to test on most recent code before complaining.
Ilia