svn: /php/php-src/branches/PHP_5_3/ README.NEW-OUTPUT-API Zend/zend_highlight.c Zend/zend_indent.c ext/iconv/iconv.c ext/session/session.c ext/soap/soap.c ext/standard/basic_functions.c ext/standard/exec.c ext/standard/head.c ext/st View as Markdown

I'd like to have branch for PHP_5_4, I'll also volunteer for RM on it.
Perhaps it makes people wanting to get movement in HEAD to actually do
something about it.

+1

We have several features still in HEAD/trunk that should be merged to
a new dev branch.

-Hannes

@jani: committing to a stable branch because you are getting a new laptop is not really a convincing argument. :)

Losing the one with the changes in it is. Doing patches will only cause endless headaches. Please move on, nothing to see here, it's all for GOOD anyway, fixing bugs USED to be okay in any branch. Besides, this is not end-of-world. If it is for someone, I suggest changing profession.

I'd like to have branch for PHP_5_4, I'll also volunteer for RM on it. Perhaps it makes people wanting to get movement in HEAD to actually do something about it.

+1

I'm all for 5.4, I have a bunch of patches against PHP_5_3 that I want to commit such a large integer support, I couldn't develop against HEAD since it's just not usable.

I think we can officially call PHP6 stalled and should move forward with 5.4 and revisit unicode support in the future.

Scott

On Thu, Mar 11, 2010 at 10:22 AM, Jani Taskinen jani.taskinen@iki.fiwrote:

@jani: committing to a stable branch because you are getting a new laptop
is not really a convincing argument. :)

Losing the one with the changes in it is. Doing patches will only cause
endless headaches. Please move on, nothing to see here, it's all for GOOD
anyway, fixing bugs USED to be okay in any branch. Besides, this is not
end-of-world. If it is for someone, I suggest changing profession.

I'd like to have branch for PHP_5_4, I'll also volunteer for RM on it.
Perhaps it makes people wanting to get movement in HEAD to actually do
something about it.

--Jani

--

+1

I see no reason why this can't be bullet number one on PHP 5.4 and we
already have someone willing to RM it. Probably a bit of an abrupt way to
kick off a new release, but somethings it takes that to get the ball moving
again.

Eric Lee Stewart

hi,

@jani: committing to a stable branch because you are getting a new laptop
is not really a convincing argument. :)

Losing the one with the changes in it is. Doing patches will only cause
endless headaches. Please move on, nothing to see here, it's all for GOOD
anyway, fixing bugs USED to be okay in any branch. Besides, this is not
end-of-world. If it is for someone, I suggest changing profession.

I'd like to have branch for PHP_5_4, I'll also volunteer for RM on it.
Perhaps it makes people wanting to get movement in HEAD to actually do
something about it.

Again, the discussion about 5.4 is premature.

I see that you created the branch already, which gives the impression
that you don't want to act in team but do whatever you want whenever
you want. Or am I missing an important discussion regarding this serie
of bad moves?

Now please revert these two commits and remove the 5.4 branch as we
have no agreement or discussion at this point. Please respect the
usual process to take decisions, even if they have to be improved,
drastically even. If you like to work on this API with 5.3, create a
specific branch, that's open and will give you the freedom you need to
modify it at wish.

Cheers,

Pierre

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