Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:102173 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 43364 invoked from network); 5 Jun 2018 17:14:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Jun 2018 17:14:31 -0000 Authentication-Results: pb1.pair.com smtp.mail=cmbecker69@gmx.de; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=cmbecker69@gmx.de; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.22 as permitted sender) X-PHP-List-Original-Sender: cmbecker69@gmx.de X-Host-Fingerprint: 212.227.17.22 mout.gmx.net Received: from [212.227.17.22] ([212.227.17.22:49763] helo=mout.gmx.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D0/11-62758-6F4C61B5 for ; Tue, 05 Jun 2018 13:14:31 -0400 Received: from [192.168.2.114] ([79.222.47.197]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0M4o41-1gDpx03AWD-00z2nu; Tue, 05 Jun 2018 19:14:27 +0200 To: Sara Golemon , Anatol Belski Cc: PHP internals , "stas@php.net" References: <29b746a4-f3e4-3b47-bb10-7363b5a7bfa7@gmx.de> Message-ID: Date: Tue, 5 Jun 2018 19:14:26 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: de-DE Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:lOzFn9oDh8BxhSZswD3vxByzQ2FF7qQfDdM1Pxo1sA8JrJlPE8C UgU7ikMgzzhMTk9BmnmLkpJGbhj3WqQmmp4xkOaTO1yG4p4iikqeD/3mLpcdbcR+KrV42Gs vGKe0//NZfABUR8Vt34XvZRfakoadabMOO759Of2OHqcp3zfMZG86xVSG6retSF6qldrj76 iEaWwON4bXDULAZNUFjBw== X-UI-Out-Filterresults: notjunk:1;V01:K0:nif+9rk6CGc=:Jsrjqu6ErclJ54Ge4n5iKO ZpnaM15+SxZChfdUnvgjqgu9x8weGqSD+7UljNU9e59imYe7wvV0FbdAV+SCtTkk5ZVjmX5tE 1tip+cxpRJgIbzIBfwKcyWBkV28hUQoTWKxPjdkAAcsOh0tS8vtCbGxqj6XrYWDWIrewt7uQk YkSyt82wlvWnUg0/nIdLyGmJ2VYbjyNVsnL0pCMqI3I96aAKmR/zkT5WFOp+inu9BhvXtkfzU 6ww0zH5BjdfQt451qzGIMOXO+MvHU0FDd8e6qU2KyAc5814c4gy+lgV9rNc4mu1oyK1rQSLm2 WOsxSSWR4GDjAHQatcB+1pZdjAhg5i8SYC9DOgQGewA3q7jhG52sgfPLnl0TwJQg8YFbmZexH YXzTSWUFuify0KuD0zyCsuwtbwp54peuPjLK0OfsTm6MxfGEeOGAHqrHMIMtPGYTDklRwBxYZ m3dLrJuSUo9QHq0eRZHusSI76r1h1S9cZrvkV/aPhxq1s4IWFBe65z4Wb13w04rsj/hlXp78C lOB60pGPS+qhZrmNdxEXH7Du8gqSwRQWOmGXJz1X8R2iQ5Bl8+0h8OpukUUEC7hMymMWZ0+kn cNfKg8yinprdYN6c48OmzRHlV/F+p0yU3ekMoq8bjRsYwfsuTZC3066BvX4WBETciTp/wLzMC 6QOIHIss9cQbVTLYN2dIxzwjkLp5sOBw5pOJLwo/vIAcftv40YPlUqTaVazi5VWK7oNR+4qmD IcjqeC/U4EGDW9Kd/Tjz51p9E5LpWmA/uFIS70cbleBEqBsgdmWVlqhoHXeGvOxFhL14rsEx9 CL94t4Z Subject: Re: [PHP-DEV] PHP 7.3 timetable From: cmbecker69@gmx.de ("Christoph M. Becker") On 05.06.2018 at 17:10, Sara Golemon wrote: > On Tue, Jun 5, 2018 at 10:26 AM, Anatol Belski wrote: > >> On Tue, 2018-06-05 at 15:36 +0200, Christoph M. Becker wrote: >> >>> Due to some pending preliminary work, I won't be able to release >>> 7.3.0alpha1 on Thursday. Unless Stas is willing to tackle the first >>> alpha, I suggest to postpone the tentative timetable[1] by a week. I >>> don't think that would be a problem, since 7.0 - 7.2 had their first >>> alphas released on the second Thursday of June as well. > > On the one hand: Timetables can be pushed, we're not curing cancer here. > On the other, that's what a second RM is for, so let's see what Stas has to say. ACK. >> By the pending work, do you mean the yet missing karma, etc. you >> mentioned in another thread? If so - actually you still could tag, >> write site news, etc. - so most of the things. With the items where >> there is no karma yet like uploading to downloads.php.net or mailing a >> moderated list could be helped. > > Indeed. Joe had key issues recently and due to not having his new key > in place in time we pushed the tarballs out of band, but they still > had his sigs and all the rest. A rough start, sure. But alphas are a > great time to make and learn from mistakes. :D That's indeed one of the issues. After quite some struggle, I've just managed to sign a tag with a quickly generated GPG key. However, I still need to create a proper GPG (including generating a revocation certificate), and of course, the key has to be signed by one or more of the previous RMs (not sure how that will work). -- Christoph M. Becker