PHP_5_3 Branched - Externals

17 years ago by Ilia Alshanetsky — view source

unread

The 5.3 branch was just created in the CVS and is now open for
development. Please remember to MFH/MFB your patches to this branch
when making your commits.

Thanks,

Ilia Alshanetsky
Release Master

17 years ago by Etienne Kneuss — view source

unread

Hello,

Thanks! I've that dynamic access of static members patch that is waiting to
be commited:
$foo::myFunc(); etc..

Here is the patch:
http://patches.colder.ch/Zend/dynamic_static_calls_5_3.patch?markup

Thanks in advance!

Regards

The 5.3 branch was just created in the CVS and is now open for
development. Please remember to MFH/MFB your patches to this branch
when making your commits.

Thanks,

Ilia Alshanetsky
Release Master

--

--
Etienne Kneuss
http://www.colder.ch

Men never do evil so completely and cheerfully as
when they do it from a religious conviction.
-- Pascal

17 years ago by johannes@php.net — view source

unread

Hi,

Hello,

Thanks! I've that dynamic access of static members patch that is waiting to
be commited:
$foo::myFunc(); etc..

Done.

johannes

Here is the patch:
http://patches.colder.ch/Zend/dynamic_static_calls_5_3.patch?markup

Thanks in advance!

Regards

The 5.3 branch was just created in the CVS and is now open for
development. Please remember to MFH/MFB your patches to this branch
when making your commits.

Thanks,

Ilia Alshanetsky
Release Master

17 years ago by Ilia Alshanetsky — view source

unread

Thanks.

Hi,

Hello,

Thanks! I've that dynamic access of static members patch that is waiting
to
be commited:
$foo::myFunc(); etc..

Done.

johannes

Here is the patch:
http://patches.colder.ch/Zend/dynamic_static_calls_5_3.patch?markup

Thanks in advance!

Regards

The 5.3 branch was just created in the CVS and is now open for
development. Please remember to MFH/MFB your patches to this branch
when making your commits.

Thanks,

Ilia Alshanetsky
Release Master

17 years ago by Ryan Panning — view source

unread

Hi, what are the chances this patch can be committed to the 5.2.x
branch? I'm working on a project which can benefit from this patch but
5.3 sounds to be a ways out.

Thanks,
Ryan Panning

Etienne Kneuss wrote:

Hello,

Thanks! I've that dynamic access of static members patch that is waiting to
be commited:
$foo::myFunc(); etc..

Here is the patch:
http://patches.colder.ch/Zend/dynamic_static_calls_5_3.patch?markup

Thanks in advance!

Regards

The 5.3 branch was just created in the CVS and is now open for
development. Please remember to MFH/MFB your patches to this branch
when making your commits.

Thanks,

Ilia Alshanetsky
Release Master

17 years ago by johannes@php.net — view source

unread

Hi, what are the chances this patch can be committed to the 5.2.x
branch? I'm working on a project which can benefit from this patch but
5.3 sounds to be a ways out.

Zero. 5.2 is a stable branch which can't get any new language feature.

johannes

Thanks,
Ryan Panning

Etienne Kneuss wrote:

Hello,

Thanks! I've that dynamic access of static members patch that is waiting to
be commited:
$foo::myFunc(); etc..

Here is the patch:
http://patches.colder.ch/Zend/dynamic_static_calls_5_3.patch?markup

Thanks in advance!

Regards

The 5.3 branch was just created in the CVS and is now open for
development. Please remember to MFH/MFB your patches to this branch
when making your commits.

Thanks,

Ilia Alshanetsky
Release Master

17 years ago by Stanislav Malyshev — view source

unread

The 5.3 branch was just created in the CVS and is now open for
development. Please remember to MFH/MFB your patches to this branch when
making your commits.

Maybe it would be a good idea to start 5.2.5 release cycle soon - so we
get rid of pending fixes and need to merge between 5.2 and 5.3?

--
Stanislav Malyshev, Zend Software Architect
stas@zend.com http://www.zend.com/
(408)253-8829 MSN: stas@zend.com

17 years ago by Ilia Alshanetsky — view source

unread

I don't think that 5.2.5 will be the last 5.2.X release before 5.3 is
released as much as I'd like that to be the case. So, the need to maintain
5.2.X branch will continue even post 5.2.5 release, but I don't disagree
with the idea of starting the process of 5.2.5 release in a week or so.

The 5.3 branch was just created in the CVS and is now open for
development. Please remember to MFH/MFB your patches to this branch when
making your commits.

Maybe it would be a good idea to start 5.2.5 release cycle soon - so we
get rid of pending fixes and need to merge between 5.2 and 5.3?

--
Stanislav Malyshev, Zend Software Architect
stas@zend.com http://www.zend.com/
(408)253-8829 MSN: stas@zend.com

17 years ago by Stanislav Malyshev — view source

unread

I don't think that 5.2.5 will be the last 5.2.X release before 5.3 is
released as much as I'd like that to be the case. So, the need to
maintain 5.2.X branch will continue even post 5.2.5 release, but I don't
disagree with the idea of starting the process of 5.2.5 release in a
week or so.

Yes, I think in a week would be OK. I just don't want to keep the
backlog in 5.2 branch provided all the real work will be in 5.3 now :)

--
Stanislav Malyshev, Zend Software Architect
stas@zend.com http://www.zend.com/
(408)253-8829 MSN: stas@zend.com

17 years ago by Jani Taskinen — view source

unread

The 5.3 branch was just created in the CVS and is now open for
development. Please remember to MFH/MFB your patches to this branch when
making your commits.

Maybe it would be a good idea to start 5.2.5 release cycle soon - so we
get rid of pending fixes and need to merge between 5.2 and 5.3?

The merging to pure bugfix branch like 5.2 now is, is the responsibility
of the RM for that branch. In this case it is Ilia.

This brings up one thing overlooked: Who is the RM for 5.3?

--Jani

--
Patches/Donations: http://pecl.php.net/~jani/

17 years ago by Lukas Kahwe Smith — view source

unread

Jani Taskinen wrote:

The 5.3 branch was just created in the CVS and is now open for
development. Please remember to MFH/MFB your patches to this branch when
making your commits.
Maybe it would be a good idea to start 5.2.5 release cycle soon - so we
get rid of pending fixes and need to merge between 5.2 and 5.3?

The merging to pure bugfix branch like 5.2 now is, is the responsibility
of the RM for that branch. In this case it is Ilia.

This brings up one thing overlooked: Who is the RM for 5.3?

I like the of getting some fresh new blood to work on this that was
brought up with the proposal of Johannes. AFAIK he already said he would
be willing to take on the job.

regards,
Lukas

17 years ago by Jani Taskinen — view source

unread

Jani Taskinen wrote:

This brings up one thing overlooked: Who is the RM for 5.3?

I like the of getting some fresh new blood to work on this that was
brought up with the proposal of Johannes. AFAIK he already said he would
be willing to take on the job.

I'm of course +1 for that. :)

--
Patches/Donations: http://pecl.php.net/~jani/

17 years ago by Pierre — view source

unread

Jani Taskinen wrote:

The 5.3 branch was just created in the CVS and is now open for
development. Please remember to MFH/MFB your patches to this branch when
making your commits.
Maybe it would be a good idea to start 5.2.5 release cycle soon - so we
get rid of pending fixes and need to merge between 5.2 and 5.3?

The merging to pure bugfix branch like 5.2 now is, is the responsibility
of the RM for that branch. In this case it is Ilia.

This brings up one thing overlooked: Who is the RM for 5.3?

I like the of getting some fresh new blood to work on this that was
brought up with the proposal of Johannes. AFAIK he already said he would
be willing to take on the job.

To be honest I would like to have you as RM. You have the background
to take the right decisions and other can help when it comes to low
level technical or security issues.

From a management, feedbacks or compromises ready point of view, you
have already proven your abilities.

Cheers,
--Pierre

17 years ago by Steph Fox — view source

unread

To be honest I would like to have you as RM. You have the background
to take the right decisions and other can help when it comes to low
level technical or security issues.

From a management, feedbacks or compromises ready point of view, you
have already proven your abilities.

Pierre definitely has a point here :) but what says Ilia?

Steph

17 years ago by Ilia Alshanetsky — view source

unread

I am a biased party here, so take this with a grain of salt ;-)

First of all, I definitely think we need 2 release masters, for 5.X
tree given that there will be two active branches, at least for the
next few months, there is simply too much work for one person to do.
My suggestion was going to be (Lukas beat me to the punch with his
proposal) that I RM 5.3 release and ask someone new to take over the
5.2 branch and within 1-2 releases of 5.3.0 have that person take
over 5.3 branch, once they are a bit more familiar with the process.
I do agree that having more people try their hand at being RM is a
very good idea and historically every minor/major release had a new RM.

To be honest I would like to have you as RM. You have the background
to take the right decisions and other can help when it comes to low
level technical or security issues.
From a management, feedbacks or compromises ready point of view, you
have already proven your abilities.

Pierre definitely has a point here :) but what says Ilia?

Steph

Ilia Alshanetsky

17 years ago by Antony Dovgal — view source

unread

I am a biased party here, so take this with a grain of salt ;-)

First of all, I definitely think we need 2 release masters, for 5.X
tree given that there will be two active branches, at least for the
next few months, there is simply too much work for one person to do.
My suggestion was going to be (Lukas beat me to the punch with his
proposal) that I RM 5.3 release and ask someone new to take over the
5.2 branch and within 1-2 releases of 5.3.0 have that person take
over 5.3 branch, once they are a bit more familiar with the process.
I do agree that having more people try their hand at being RM is a
very good idea and historically every minor/major release had a new RM.

Sounds like a plan to me.

--
Wbr,
Antony Dovgal

17 years ago by Andi Gutmans — view source

unread

+1 and I think it's a good way for someone to get into the role.

-----Original Message-----
From: Ilia Alshanetsky [mailto:ilia@prohost.org]
Sent: Thursday, September 27, 2007 11:07 AM
To: Steph Fox
Cc: Lukas Kahwe Smith; jani.taskinen@iki.fi; Stas Malyshev; PHP
Developers Mailing List; Pierre
Subject: Re: [PHP-DEV] PHP_5_3 Branched

I am a biased party here, so take this with a grain of salt ;-)

First of all, I definitely think we need 2 release masters, for 5.X
tree given that there will be two active branches, at least for the
next few months, there is simply too much work for one person to do.
My suggestion was going to be (Lukas beat me to the punch with his
proposal) that I RM 5.3 release and ask someone new to take over the
5.2 branch and within 1-2 releases of 5.3.0 have that person take
over 5.3 branch, once they are a bit more familiar with the process.
I do agree that having more people try their hand at being RM is a
very good idea and historically every minor/major release had a new
RM.

To be honest I would like to have you as RM. You have the
background
to take the right decisions and other can help when it comes to low
level technical or security issues.
From a management, feedbacks or compromises ready point of view,
you
have already proven your abilities.

Pierre definitely has a point here :) but what says Ilia?

Steph

Ilia Alshanetsky

17 years ago by Lukas Kahwe Smith — view source

unread

Andi Gutmans wrote:

+1 and I think it's a good way for someone to get into the role.

I do not see why we need this delayed hand over. RMs managed to take
over during the process in the past and today we even have a check list
for this purpose. The main challenge is managing the politics on this
list and we all know how this works. Of course there are also technical
issues to take care of (like monitoring the commits so that nothing ends
up in the release that was not intended).

If the process itself needs further clarification we should improve the
documentation. Of course previous RMs are also around for a new RM to
answer questions. But I think its a good tradition to switch RMs to
ensure that the experienced remains shared and that we do not end up
with a lot of single person specific implicit processes.

Anyways, I am here to help any RM that is put into the position (I lack
the technical expertise to handle this stuff, so I should better stick
with the secretary job) and I am sure Ilia will continue to do a good
job. I also believe that Johannes will do a good job (of course he will
need the support of previous RMs) if he takes the job.

regards,
Lukas

17 years ago by Steph Fox — view source

unread

Hi Lukas,

I do not see why we need this delayed hand over. RMs managed to take over
during the process in the past and today we even have a check list for
this purpose. The main challenge is managing the politics on this list and
we all know how this works. Of course there are also technical issues to
take care of (like monitoring the commits so that nothing ends up in the
release that was not intended).

...etc. I'd argue that we do need a delayed handover. The PHP project has
grown massively over the last 5 years - basically, it grew up.

So I'm with Ilia over all that. The question is who? Used to be that whoever
felt they had the time to do it could, so long as nobody fought the
proposal. I don't see anyone fighting against your proposal for Johannes (I
wouldn't either) but I also agree with Pierre's diagnosis, that you'd be
good at the job.

Does there need to be a vote over this, or is there only one volunteer?

Steph

17 years ago by Lukas Kahwe Smith — view source

unread

Steph Fox wrote:

So I'm with Ilia over all that. The question is who? Used to be that
whoever felt they had the time to do it could, so long as nobody fought
the proposal. I don't see anyone fighting against your proposal for
Johannes (I wouldn't either) but I also agree with Pierre's diagnosis,
that you'd be good at the job.

Since I already stated that I am only interested in the part of the job
that does not require php-src karma, I am probably not a good fit. I
would definitely change the job scope. As such I think Johannes is then
still the best option for this delayed take over because he can take the
full job and because he is fresh young blood to train for the next
decades of PHP :)

regards,
Lukas

17 years ago by Steph Fox — view source

unread

Since I already stated that I am only interested in the part of the job
that does not require php-src karma, I am probably not a good fit. I
would definitely change the job scope. As such I think Johannes is then
still the best option for this delayed take over because he can take the
full job and because he is fresh young blood to train for the next
decades of PHP :)

This is too easy - are we posting to the right list? :)

Good luck Johannes!

Steph

17 years ago by Michael Wallner — view source

unread

Ilia Alshanetsky wrote:

I am a biased party here, so take this with a grain of salt ;-)

First of all, I definitely think we need 2 release masters, for 5.X tree
given that there will be two active branches, at least for the next few
months, there is simply too much work for one person to do. My
suggestion was going to be (Lukas beat me to the punch with his
proposal) that I RM 5.3 release and ask someone new to take over the 5.2
branch and within 1-2 releases of 5.3.0 have that person take over 5.3
branch, once they are a bit more familiar with the process. I do agree
that having more people try their hand at being RM is a very good idea
and historically every minor/major release had a new RM.

I like that idea, too... but I don't think that Johannes would have big
problems starting with 5.3.0. Anyway, I'd like to see Johannes as RM
for 5.3--now or a bit later.

--
Michael

17 years ago by Ilia Alshanetsky — view source

unread

I spoke to Johannes and few other core developers and I think it is
time we give someone new a shot at the helm. I've been doing 5.X
RMing since 5.0.3 (almost 2 years now, seems like forever) and its
time for some fresh perspective, I think 5.3 will prove a good time
for that to keep with our tradition of changing RMs on every minor
release.

We have well documented (Thanks to Lukas) RMing processes now that
should make the bureaucracy ;-) a little simpler and I feel Johannes
definitely has enough technical awareness of the various parts of PHP
to do a great job at the RM role.

Unless any objections are raised, or someone else wants to throw
their hat into the mix, I'd like to confirm Johannes at his new role
as 5.3 RM and wish him the best of luck and much co-operation from
all developers.

In the mean time, I will continue to RM the 5.2.X release, which will
continue to be actively maintained up until 5.3 is released and use
this opportunity to provide 2 week notice of the upcoming 5.2.5RC1,
so please, get your pending fixes in. The goal is get 5.2.5 out early/
mid November.

Ilia Alshanetsky
5.2 Release Master

17 years ago by David Coallier — view source

unread

I spoke to Johannes and few other core developers and I think it is
time we give someone new a shot at the helm. I've been doing 5.X
RMing since 5.0.3 (almost 2 years now, seems like forever) and its
time for some fresh perspective, I think 5.3 will prove a good time
for that to keep with our tradition of changing RMs on every minor
release.

We have well documented (Thanks to Lukas) RMing processes now that
should make the bureaucracy ;-) a little simpler and I feel Johannes
definitely has enough technical awareness of the various parts of PHP
to do a great job at the RM role.

Unless any objections are raised, or someone else wants to throw
their hat into the mix, I'd like to confirm Johannes at his new role
as 5.3 RM and wish him the best of luck and much co-operation from
all developers.

In the mean time, I will continue to RM the 5.2.X release, which will
continue to be actively maintained up until 5.3 is released and use
this opportunity to provide 2 week notice of the upcoming 5.2.5RC1,
so please, get your pending fixes in. The goal is get 5.2.5 out early/
mid November.

Thanks for all that work Ilia, and congrats to you Johannes

Ilia Alshanetsky
5.2 Release Master

--

--
David Coallier,
Founder & Software Architect,
Agora Production (http://agoraproduction.com)
51.42.06.70.18

17 years ago by Sebastian Bergmann — view source

unread

David Coallier schrieb:

Thanks for all that work Ilia, and congrats to you Johannes

Hear, hear!

--
Sebastian Bergmann http://sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69

17 years ago by Andi Gutmans — view source

unread

Ilia,

Thanks a lot for the great job you've done (and the job you will
continue doing on PHP 5.2.x, security and as a contributor in general).
You have shown true leadership throughout the releases and have been
very good at making the quality/features trade-offs.

Johannes, best of luck. PHP 5.3 is going to be a huge release for PHP
and I'm sure you'll be successful in helping us get there.

Andi

-----Original Message-----
From: Ilia Alshanetsky [mailto:ilia@prohost.org]
Sent: Saturday, September 29, 2007 8:45 AM
To: PHP Developers Mailing List
Subject: [PHP-DEV] PHP 5.3 RM / PHP 5.2.5RC1

I spoke to Johannes and few other core developers and I think it is
time we give someone new a shot at the helm. I've been doing 5.X
RMing since 5.0.3 (almost 2 years now, seems like forever) and its
time for some fresh perspective, I think 5.3 will prove a good time
for that to keep with our tradition of changing RMs on every minor
release.

We have well documented (Thanks to Lukas) RMing processes now that
should make the bureaucracy ;-) a little simpler and I feel Johannes
definitely has enough technical awareness of the various parts of PHP
to do a great job at the RM role.

Unless any objections are raised, or someone else wants to throw
their hat into the mix, I'd like to confirm Johannes at his new role
as 5.3 RM and wish him the best of luck and much co-operation from
all developers.

In the mean time, I will continue to RM the 5.2.X release, which will
continue to be actively maintained up until 5.3 is released and use
this opportunity to provide 2 week notice of the upcoming 5.2.5RC1,
so please, get your pending fixes in. The goal is get 5.2.5 out early/
mid November.

Ilia Alshanetsky
5.2 Release Master

17 years ago by johannes@php.net — view source

unread

Hi,

I spoke to Johannes and few other core developers and I think it is
time we give someone new a shot at the helm. I've been doing 5.X
RMing since 5.0.3 (almost 2 years now, seems like forever) and its
time for some fresh perspective, I think 5.3 will prove a good time
for that to keep with our tradition of changing RMs on every minor
release.

We have well documented (Thanks to Lukas) RMing processes now that
should make the bureaucracy ;-) a little simpler and I feel Johannes
definitely has enough technical awareness of the various parts of PHP
to do a great job at the RM role.

Unless any objections are raised, or someone else wants to throw
their hat into the mix, I'd like to confirm Johannes at his new role
as 5.3 RM and wish him the best of luck and much co-operation from
all developers.

Thanks for all the support - I'll, of course, take the chance of taking
over RMing and hope we all make 5.3 a good series. Ilia, thanks for
offering assistance - it would be bad to loose your experience :-)

johannes

17 years ago by Antony Dovgal — view source

unread

I like the of getting some fresh new blood to work on this that was
brought up with the proposal of Johannes. AFAIK he already said he would
be willing to take on the job.

I like the way Ilia did (still does) his job in 5_2, so I would prefer Ilia to switch to 5_3
and somebody else to take over 5_2 maintenance.

--
Wbr,
Antony Dovgal

17 years ago by Andi Gutmans — view source

unread

I also think Ilia has had a good track record of getting to the right
compromises & balances for the releases. It may be a good idea to have
him continue one more release especially as this is quite a big and
loaded release.
If not, let's get a better understanding of who the candidates are and
what their experience is with PHP development. We have to dive quite
deep with RM on technical issues & patches so we need someone very
strong like Ilia.

Andi

-----Original Message-----
From: Antony Dovgal [mailto:tony@daylessday.org]
Sent: Thursday, September 27, 2007 8:12 AM
To: Lukas Kahwe Smith
Cc: jani.taskinen@iki.fi; Stas Malyshev; Ilia Alshanetsky; PHP
Developers Mailing List
Subject: Re: [PHP-DEV] PHP_5_3 Branched

I like the of getting some fresh new blood to work on this that was
brought up with the proposal of Johannes. AFAIK he already said he
would
be willing to take on the job.

I like the way Ilia did (still does) his job in 5_2, so I would prefer
Ilia to switch to 5_3
and somebody else to take over 5_2 maintenance.

--
Wbr,
Antony Dovgal