RC3 did not prove as stable as I hoped it would be, so here we are 20+ bug
fixes later with RC4. It is my sincere hope that RC4 will be the last RC
before we can proceed with the final. Please test this release as much as
possible, ideally you won't find any new bugs.
Once again I would like to ask that all developers refrain from making commits
to the 4_3 tree until 4.3.3 final is released, unless a patch addresses a
critical issue. Critical issues are defined as the following:
- Security Fixes
- Fixes for bugs introduced in 4.3.3X releases
- Fixes for bugs that break backwards compatibility with older versions.
Ilia
Is php.announce no longer used for announcements like this?
--
Martin
"Let's dance in style, Let's dance for a while"
Not for RC's AFAIK...
--
// DvDmanDT
MSN: dvdmandt@hotmail.com
Mail: dvdmandt@telia.com
"Martin Koch Andersen" function@tiscali.dk skrev i meddelandet
news:20030818164050.73285.qmail@pb1.pair.com...
Is php.announce no longer used for announcements like this?
--
Martin
"Let's dance in style, Let's dance for a while"
Hi,
I have a patch for the Informix extensions that fixes a bug which is
quite old, but a big problem (Related bugs: 13459, 8267, 14254, 19416,
16145, 14314).
Can i commit this to the PHP_4_3 branch and can it be included in
PHP-4.3.3 final ?
or do i need to commit it to PHP_4 now, and to PHP_4_3 after 4.3.3
final is released ?
Thanks,
Corne'
!Exclude Disclaimer!
Ilia Alshanetsky wrote:
RC3 did not prove as stable as I hoped it would be, so here we are 20+ bug
fixes later with RC4. It is my sincere hope that RC4 will be the last RC
before we can proceed with the final. Please test this release as much as
possible, ideally you won't find any new bugs.Once again I would like to ask that all developers refrain from making commits
to the 4_3 tree until 4.3.3 final is released, unless a patch addresses a
critical issue. Critical issues are defined as the following:
- Security Fixes
- Fixes for bugs introduced in 4.3.3X releases
- Fixes for bugs that break backwards compatibility with older versions.
Ilia
I have a patch for the Informix extensions that fixes a bug which is
quite old, but a big problem (Related bugs: 13459, 8267, 14254, 19416,
16145, 14314).
Can i commit this to the PHP_4_3 branch and can it be included in
PHP-4.3.3 final ?
Nope, if Ilia doesn't shoout you for that, I will ;)
or do i need to commit it to PHP_4 now, and to PHP_4_3 after 4.3.3
final is released ?
No, do not commit it to PHP_4. I think you're safe to commit it to
PHP_4_3, because we normally just release the final from the tags of the
latest RC... but I'm not sure if Ilia wants to do that too.
Derick
--
"Interpreting what the GPL actually means is a job best left to those
that read the future by examining animal entrails."
Derick Rethans http://derickrethans.nl/
International PHP Magazine http://php-mag.net/
I have a patch for the Informix extensions that fixes a bug which is
quite old, but a big problem (Related bugs: 13459, 8267, 14254, 19416,
16145, 14314).
Can i commit this to the PHP_4_3 branch and can it be included in
PHP-4.3.3 final ?or do i need to commit it to PHP_4 now, and to PHP_4_3 after 4.3.3
final is released ?
No, commit to HEAD..
--Jani
At this stage it is already too late for patches for the 4.3.3 release. You
can still commit your patch to HEAD (PHP 5.0) and MFH it to PHP_4_3, but you
should know that the fix will not be part of the 4.3.3 release. Pending any
critical issues 4.3.3 will be released based upon RC4.
Ilia
. Please commit your patch to HEAD (PHP 5.0)
Hi,
I have a patch for the Informix extensions that fixes a bug which is
quite old, but a big problem (Related bugs: 13459, 8267, 14254, 19416,
16145, 14314).
Can i commit this to the PHP_4_3 branch and can it be included in
PHP-4.3.3 final ?or do i need to commit it to PHP_4 now, and to PHP_4_3 after 4.3.3
final is released ?