Sorry to break up the allow_url_fopen discussion but I think that thread is
getting a bit old already and definitely clogging up the mailing list.
(hint hint)
I'd like to start moving forward with the 5.1.0 release process. It seems
we are in quite good shape but as we have had many patches since Beta 2 we
definitely need another Beta. There is also an sqlite upgrade coming within
a day.
I suggest to release Beta 3 in a bit over a week (Friday, July 8th), and
then go into a feature freeze towards RC1. Depending on the stability, I'd
aim for RC1 within two weeks of the beta (branching it off to PHP_5_1) and
then start merging Unicode work into HEAD. This merge will probably take a
couple of weeks and will be done mainly by Andrei and Dmitry. At that time,
we shouldn't disrupt the tree too much as the merge will be quite hard.
As far as PHP_5_0 branch is concerned. We should slowly fade it out but I
suggest to still commit important fixes as we might find ourselves in a
situation where we need to release additional mini releases (critical bugs,
security bugs, etc).
So to summarize a schedule I suggest:
a) 5.1.0 Beta 3 Friday, July 8th.
b) Release & branch 5.1.0 RC1 July 15-22nd
c) Mid-July start merging Unicode into HEAD. Until end of July minimum
changes to HEAD.
I think it's a good balance between releasing a stable 5.1.0 and allowing
the Unicode support to make good progress and give a chance to a larger
audience to help out adding Unicode support to extensions.
Anyone who still has some comments or fixes/modifications to commit before
Beta 3 please let me know...
Thanks.
Andi
On Wed, 29 Jun 2005 18:10:15 -0700
andi@zend.com (Andi Gutmans) wrote:
Sorry to break up the allow_url_fopen discussion but I think that
thread is getting a bit old already and definitely clogging up
the mailing list. (hint hint)I'd like to start moving forward with the 5.1.0 release process.
It seems we are in quite good shape but as we have had many
patches since Beta 2 we definitely need another Beta. There is
also an sqlite upgrade coming within a day.I suggest to release Beta 3 in a bit over a week (Friday, July
8th), and then go into a feature freeze towards RC1. Depending on
the stability, I'd aim for RC1 within two weeks of the beta
(branching it off to PHP_5_1) and then start merging Unicode work
into HEAD. This merge will probably take a couple of weeks and
will be done mainly by Andrei and Dmitry. At that time, we
shouldn't disrupt the tree too much as the merge will be quite
hard.As far as PHP_5_0 branch is concerned. We should slowly fade it
out but I suggest to still commit important fixes as we might
find ourselves in a situation where we need to release additional
mini releases (critical bugs, security bugs, etc).So to summarize a schedule I suggest:
a) 5.1.0 Beta 3 Friday, July 8th.
b) Release & branch 5.1.0 RC1 July 15-22nd
c) Mid-July start merging Unicode into HEAD. Until end of July
minimum changes to HEAD.I think it's a good balance between releasing a stable 5.1.0 and
allowing the Unicode support to make good progress and give a
chance to a larger audience to help out adding Unicode support to
extensions.
Nice plan thanks :)
I would like to have 5.1 branches. Stopping the developements for
nearly a month for an already feautures freezed release. What's
branche it after beta2?
Regards,
--Pierre
So to summarize a schedule I suggest:
a) 5.1.0 Beta 3 Friday, July 8th.
b) Release & branch 5.1.0 RC1 July 15-22nd
c) Mid-July start merging Unicode into HEAD. Until end of July
minimum changes to HEAD.I think it's a good balance between releasing a stable 5.1.0 and
allowing the Unicode support to make good progress and give a
chance to a larger audience to help out adding Unicode support to
extensions.I would like to have 5.1 branches. Stopping the developements for
nearly a month for an already feautures freezed release. What's
branche it after beta2?
What are you planning to do in those 3 weeks?
Personally, I'd find it really irritating to have to merge across branches
for PDO changes in that timespan. Unless it's really important, we should
avoid creating branches. Keep in mind that the tree will be mostly frozen
while the unicode stuff is merged in too.
--Wez.
On Thu, 30 Jun 2005 07:52:04 -0400
Wez Furlong kingwez@gmail.com wrote:
So to summarize a schedule I suggest:
a) 5.1.0 Beta 3 Friday, July 8th.
b) Release & branch 5.1.0 RC1 July 15-22nd
c) Mid-July start merging Unicode into HEAD. Until end of July
minimum changes to HEAD.I think it's a good balance between releasing a stable 5.1.0
and allowing the Unicode support to make good progress and
give a chance to a larger audience to help out adding Unicode
support to extensions.I would like to have 5.1 branches. Stopping the developements
for nearly a month for an already feautures freezed release.
What's branche it after beta2?What are you planning to do in those 3 weeks?
I have 2 things in mind now (ext/date being out of my mind
actually....):
ext/gd
- sync with official GD (both directions this time)
- gif write mode and partial rewrite of the read mode.
- Drop GD1 extern support
- Drop FT1 support
ext/xmlwriter
include it so it "can" be tested
Personally, I'd find it really irritating to have to merge across
branches for PDO changes in that timespan. Unless it's really
important, we should avoid creating branches. Keep in mind that
the tree will be mostly frozen while the unicode stuff is merged
in too.
I know how annoying it is :)
That raises again the possible need to split ext/* from the "core"
repository, all together 5.1 stops commits for 2 months until it is
released, sounds a bit too much to me. Am I alone to have some
spare times during summer hollydays? ;)
However, not like I will not survive to do not commit, not the 1st
time for 5.1 ;) So if everyone likes to stop public developements
during the whole 5.1 releases phases, fine with me.
Regards,
--Pierre
Andi,
The merge Andrei and Dmitry will be performing will for the most part be
limited to Zend/ main/* and ext/standard/*. IMHO it makes little sense
to lock the entire tree with dozens of modules for features and other
improvements, between 5.1 release and UNICODE merge.
Ilia
Ilia,
I think that makes sense. When we branch I'll ask them to give clear
guidelines as to what shouldn't be touched. Your list is probably very
close to reality.
Andi
At 09:22 AM 6/30/2005 -0400, Ilia Alshanetsky wrote:
Andi,
The merge Andrei and Dmitry will be performing will for the most part be
limited to Zend/ main/* and ext/standard/*. IMHO it makes little sense to
lock the entire tree with dozens of modules for features and other
improvements, between 5.1 release and UNICODE merge.Ilia
may zend_vm_set_opcode_handler be exported with ZEND_API?
Hi,
It's already exported.
Andi
At 01:06 AM 7/1/2005 +0800, Xuefer wrote:
may zend_vm_set_opcode_handler be exported with ZEND_API?
how about
<?php
$GLOBALS['a'] = '';
$GLOBALS['a'] .= '/' . $_SERVER['SERVER_NAME'];
?>
/usr/src/php5/Zend/zend_operators.c(1179) : Freeing 0x1015C2C8 (11
bytes), script=/www/test.php
=== Total 1 memory leaks detected ===
but there was no problem untill i do "cvs up" and rebuild recently
I'd like to start moving forward with the 5.1.0 release process. It seems
we are in quite good shape but as we have had many patches since Beta 2 we
definitely need another Beta. There is also an sqlite upgrade coming within
a day.
Please fix the Bug#33520 or at least revert the patch for session_path with
safe_mode. It dumps core badly.
--
.''. Piotr Roszatycki, Netia SA : :' : mailto:Piotr_Roszatycki@netia.net.pl. ' mailto:dexter@debian.org