Re: svn: /php/php-src/branches/
| From: | Hannes Magnusson | Date: | Fri, 12 Mar 2010 13:51:17 +0000 |
| Subject: | Re: svn: /php/php-src/branches/ | ||
| References: | 1 2 3 4 5 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-62041@lists.php.net to get a copy of this message | ||
On Fri, Mar 12, 2010 at 14:43, Lukas Kahwe Smith <mls@pooteeweet.org> wrote:
>
> On 12.03.2010, at 14:21, Pierre Joye wrote:
>
>> On Fri, Mar 12, 2010 at 12:29 PM, Hannes Magnusson
>> <hannes.magnusson@gmail.com> wrote:
>>> On Fri, Mar 12, 2010 at 10:57, Pierre Joye <pierre.php@gmail.com> wrote:
>>>> On Thu, Mar 11, 2010 at 5:09 PM, Jani Taskinen <jani@php.net> wrote:
>>>>> jani Thu, 11 Mar 2010
>>>>> 16:09:37 +0000
>>>>>
>>>>> Revision:
>>>>> http://svn.php.net/viewvc?view=revision&revision=296076
>>>>>
>>>>> Log:
>>>>> Hello PHP 5.4, open for all new stuff.
>>>>
>>>> Instead of persisting into doing whatever you feel or want, what are
>>>> you waiting for to revert your commits as requested numerous times
>>>> already?
>>>
>>> The numerous requests for moving trunk to branches/UNICODE_EXPERIMENT
>>> is the reason.
>>> There no reason to kill this branch. As soon as trunk has been moved,
>>> this branch will become the next trunk/
>>
>> Confusions, wrong messages, bad suggestions, no reason to hurry up
>> without a real plan, etc. Those are all very good reasons not to do
>> it this way, especially not because someone had yet another crazy day.
>> PHP really does not need such events, as our reputations about
>> releases managements is slowly getting better...
>
>
> Because no decision has been made. Jani is creating facts without basis. Furthermore normal
> development is continuing on the branches we decided to have. Now there is suddenly a 5.4. The point
> in time when we branch off a new trunk shouldn't be Jani deciding this because he is pissed off
> because there are open OB bugs.
>
> So I am all for getting excited again about moving php forward, but lets not loose our head
> over this. Jani has done the first step in cleaning up his mess. The next step is removing _his_ 5_4
> branch. I do not see this as negotiable and its not about proofing a point. Its simply not sensible
> to keep this branch and confuse the hell out of everyone.
>
I'm confused by your confusion.
There is a thread on internals on exactly this. Moving trunk and
rename "his" branch to trunk.
It seems to me we are just waiting for it to happen.
-Hannes