It has been a while since our last release and we have a fair number of
bug fixes and minor improvements accumulated, so it's time for 5.1.3. My
goal is to have the release out by March 30th, with 2 RCs between now
and then to let us test everything out.
Plan:
March 9, 2006
Initial RC1, from this point on only bug fixes should go into the 5.1
branch and I'd like to ask that any major changes (due to a bug fix) to
the code base are run by me. This means that you have just under a week
to "sneak in" any remaining minor features ;-).
March 23, 2006
RC2 (final one), only critical bug fixes (security fixes and regression
fixes) from this point on. If we get any between 23rd and 30th, we'll
probably need additional RCs.
March 29-30, 2006
New 5.1.3 packaged and released.
Pretty short plan, so hopefully Mr. Murphy will not interfere too much
with its execution ;-).
Ilia
Ilia Alshanetsky wrote:
It has been a while since our last release and we have a fair number of
bug fixes and minor improvements accumulated, so it's time for 5.1.3. My
goal is to have the release out by March 30th, with 2 RCs between now
and then to let us test everything out.
I have updated the 5.1.x release management page on my wiki accordingly.
If anyone has any features he is planning to "squeeze" into this release
please let me know so I can add it there to assist Ilia in the release
management:
http://oss.backendmedia.com/PhP51
regards,
Lukas
Ilia,
I'd like to import the latest release of PCRE before you roll RC1. I
should be able to do it before March 9, though.
-Andrei
It has been a while since our last release and we have a fair
number of bug fixes and minor improvements accumulated, so it's
time for 5.1.3. My goal is to have the release out by March 30th,
with 2 RCs between now and then to let us test everything out.Plan:
March 9, 2006
Initial RC1, from this point on only bug fixes should go into the
5.1 branch and I'd like to ask that any major changes (due to a bug
fix) to the code base are run by me. This means that you have just
under a week to "sneak in" any remaining minor features ;-).March 23, 2006
RC2 (final one), only critical bug fixes (security fixes and
regression fixes) from this point on. If we get any between 23rd
and 30th, we'll probably need additional RCs.March 29-30, 2006
New 5.1.3 packaged and released.
Pretty short plan, so hopefully Mr. Murphy will not interfere too
much with its execution ;-).Ilia
Sure, I don't see any problem with that.
Ilia
Andrei Zmievski wrote:
Ilia,
I'd like to import the latest release of PCRE before you roll RC1. I
should be able to do it before March 9, though.-Andrei
It has been a while since our last release and we have a fair number
of bug fixes and minor improvements accumulated, so it's time for
5.1.3. My goal is to have the release out by March 30th, with 2 RCs
between now and then to let us test everything out.Plan:
March 9, 2006
Initial RC1, from this point on only bug fixes should go into the 5.1
branch and I'd like to ask that any major changes (due to a bug fix)
to the code base are run by me. This means that you have just under a
week to "sneak in" any remaining minor features ;-).March 23, 2006
RC2 (final one), only critical bug fixes (security fixes and
regression fixes) from this point on. If we get any between 23rd and
30th, we'll probably need additional RCs.March 29-30, 2006
New 5.1.3 packaged and released.
Pretty short plan, so hopefully Mr. Murphy will not interfere too much
with its execution ;-).Ilia
Done.
Sure, I don't see any problem with that.
Ilia
Andrei Zmievski wrote:
Ilia,
I'd like to import the latest release of PCRE before you roll RC1. I
should be able to do it before March 9, though.
-AndreiIt has been a while since our last release and we have a fair number
of bug fixes and minor improvements accumulated, so it's time for
5.1.3. My goal is to have the release out by March 30th, with 2 RCs
between now and then to let us test everything out.Plan:
March 9, 2006
Initial RC1, from this point on only bug fixes should go into the
5.1 branch and I'd like to ask that any major changes (due to a bug
fix) to the code base are run by me. This means that you have just
under a week to "sneak in" any remaining minor features ;-).March 23, 2006
RC2 (final one), only critical bug fixes (security fixes and
regression fixes) from this point on. If we get any between 23rd and
30th, we'll probably need additional RCs.March 29-30, 2006
New 5.1.3 packaged and released.
Pretty short plan, so hopefully Mr. Murphy will not interfere too
much with its execution ;-).Ilia
Sounds like a plan to me.
Andi
At 09:27 AM 3/5/2006, Ilia Alshanetsky wrote:
It has been a while since our last release and we have a fair number
of bug fixes and minor improvements accumulated, so it's time for
5.1.3. My goal is to have the release out by March 30th, with 2 RCs
between now and then to let us test everything out.Plan:
March 9, 2006
Initial RC1, from this point on only bug fixes should go into the
5.1 branch and I'd like to ask that any major changes (due to a bug
fix) to the code base are run by me. This means that you have just
under a week to "sneak in" any remaining minor features ;-).March 23, 2006
RC2 (final one), only critical bug fixes (security fixes and
regression fixes) from this point on. If we get any between 23rd and
30th, we'll probably need additional RCs.March 29-30, 2006
New 5.1.3 packaged and released.
Pretty short plan, so hopefully Mr. Murphy will not interfere too
much with its execution ;-).Ilia