Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50425 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 56261 invoked from network); 23 Nov 2010 09:55:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Nov 2010 09:55:57 -0000 Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.42 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 74.125.83.42 mail-gw0-f42.google.com Received: from [74.125.83.42] ([74.125.83.42:59341] helo=mail-gw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 49/4E-59959-99F8BEC4 for ; Tue, 23 Nov 2010 04:55:44 -0500 Received: by gwb10 with SMTP id 10so5230719gwb.29 for ; Tue, 23 Nov 2010 01:55:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=NE1QaZ4rprQX/AE0D/44G9TVpICnODtJUzPwRUL0hx0=; b=tr0ES1HMr95Yf1SeG8c65OgrF6gOVBYIbgFcD3m7l1sntAESyd3urSZ1Zs1UK0H4/r 2pKOuMNE3FZFqYC7G3Eaprn93P+5IFk1sknbpHmqY9VaVr1ULVeJBZEhCY6lZIVCWsK2 QYqQYDRE2KDB53OaL99nZ+AuY4UQ8UGRlUOjw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=SgnhYKL21MJuBJnLA9Vzlv36lhDq+BHh8VUbIruT33J2L728EV77SUyigR0OtVcm4n kwkzRfxhbkZ5jQwfQYKeu4LOOjE3HyAy/tyV98DmKslWv8axWgNnC9r78gwQsIee6ojb UcWdIM06dthK5lXBbtUq/Wn+tDRjA0gickv0Y= MIME-Version: 1.0 Received: by 10.150.202.12 with SMTP id z12mr11581119ybf.110.1290506129737; Tue, 23 Nov 2010 01:55:29 -0800 (PST) Sender: tyra3l@gmail.com Received: by 10.90.53.4 with HTTP; Tue, 23 Nov 2010 01:55:29 -0800 (PST) In-Reply-To: References: Date: Tue, 23 Nov 2010 10:55:29 +0100 X-Google-Sender-Auth: E9J2zoeHLgZkDmY2HJo0IA1ylp0 Message-ID: To: Patrick ALLAERT Cc: Felipe Pena , internals Content-Type: multipart/alternative; boundary=000e0cd4d25e718a440495b55f11 Subject: Re: [PHP-DEV] Hold off 5.4 From: info@tyrael.hu (Ferenc Kovacs) --000e0cd4d25e718a440495b55f11 Content-Type: text/plain; charset=UTF-8 On Tue, Nov 23, 2010 at 10:35 AM, Patrick ALLAERT wrote: > 2010/11/23 Felipe Pena : > > 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 --000e0cd4d25e718a440495b55f11--