On Tue, Nov 23, 2010 at 10:35 AM, Patrick ALLAERT <patrickalla...@php.net>wrote:
> 2010/11/23 Felipe Pena <felipe...@gmail.com>:
> > Given the current state of trunk, I think 5.4 release process should
> > not begin tomorrow (alpha or whatever other status). There are
> > numerous identified issues that we need to fix before even think to
> > begin with a release. For example:
> >
> > - type hinting (or strict hinting)
> > - no consensus
> > - the RFCs are unclear
> > - BC break introduced
> > . classes named as any of the type hint scalar types
> > do not work anymore
> > aka class int {}
> >
> > - Traits may not be ready yet for pre-release
> > - see http://svn.php.net/viewvc?view=revision&revision=298348
> > - APC support
> >
> > - There are many changes not BC with 5.x, as we allowed them for the
> > development tree, before 5.4 was even a topic
> >
> > - APC is not yet bundled. Having the opcode bundle can raise issues by
> > one or another, we should have it in from the very 1st release
> >
> > - pecl/http was planned to be bundled. What's the status?
> >
> > We also have no plan about what will or will not be 5.4. This looks
> > familiar, this is exactly how we begun 5.3 and it tooks literally
> > years to be released. There is also actually no agreement to begin
> > with 5.4 now.
> >
> > 5.4 should be hold off until we solved the listed issues and the
> > release management RFC gets discussed and hopefully approved.
> >
> > Thanks.
> >
> > --
> > Regards,
> > Felipe Pena
> >
>
> Nor do we have a clear roadmap concerning the removal of magic quotes!
> Most would like to get rid of them, but some have concerns about doing
> it in 5.4.
> (Please, use the "Magic quotes in trunk" thread to comment on this
> one: http://news.php.net/php.internals/50301)
>
>
And not just the magic quotes:
http://www.pubbs.net/201011/php/28851-re-php-dev-magic-quotes-in-trunk.html
with the current trunk, we dropped many deprecated legacy feature, which is
nice, but breaks bc with a minor version.
So I would favor a more sophisticated development and release
policy/standard.
and the current release is a "good" example why this is needed:
first Rasmus and others said, that we shouldn't plan beforehand the next
release, just start coding, and when we have enough staff, we can discuss
and vote on the version number, release managers, what will be included in
the release.
then after some time, "magically" the RM's were selected (I didn't see the
voting, maybe it happened via irc), and the 5.4 was selected for the next
version without vote (maybe irc...), and there were selected a few change
from the trunk for discussion, the most of them was included to the release
without formal approval.
:/
Tyrael
