Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:92699 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 39232 invoked from network); 24 Apr 2016 17:49:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Apr 2016 17:49:11 -0000 Authentication-Results: pb1.pair.com header.from=pthreads@pthreads.org; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=pthreads@pthreads.org; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pthreads.org from 209.85.161.171 cause and error) X-PHP-List-Original-Sender: pthreads@pthreads.org X-Host-Fingerprint: 209.85.161.171 mail-yw0-f171.google.com Received: from [209.85.161.171] ([209.85.161.171:35686] helo=mail-yw0-f171.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DD/14-13951-5170D175 for ; Sun, 24 Apr 2016 13:49:09 -0400 Received: by mail-yw0-f171.google.com with SMTP id g133so148751672ywb.2 for ; Sun, 24 Apr 2016 10:49:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pthreads-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=ROp+20UiQriTdfijmAmUJkeD2SDnyWy3ElrjsGpbf5A=; b=YIz0NPbd4JDpdlnCnr/qVGjERyJu2VM5Qa2xpjf4/0/zlczCOW/wyWjJAF514V18SZ qVkLAQ8s8HGUXGIA1Zc8XF1AI0imZ5OG7+2SkZdGSYpCK5dCrXTCzo1z5USiYGu/05/H TC5aYMeBFaMIMTl8bTV0u4X4dLv2i7r2dHqUaQo0rMbSTFQW9J0p1KtLM0oGXrawntAN MzlujIZ9NW6+xKO1RS1MHNqrSrDcVTlpb5EuQgIrjwixdjVSWUUNKDvWEB2wnRtGLpMB QdaCMwHlPgJRy8frsSYKqtIJCOZwRM0pO1dcCPcnAmNDo9ifLMZQVAikwavAcZLeFVlP niUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=ROp+20UiQriTdfijmAmUJkeD2SDnyWy3ElrjsGpbf5A=; b=WV4CvaIhG2uc3B6Hyj+/ZGmC+QG+kU4YRguQR4g9Q39r+fuSptFfdtaJUBJBMl3d4G +pmWaKEjakjw6YB9sptVpn/SBZ0uO9NqugO+eFsyLT0KJlIumy+nyQns9G83wvV3ERWR 1NLEgS+P1BpXzP/wg546+TojPUiScuWlAAQOzv7d8K0O7H8S5GCi9bfwqavVQ6I4yoVQ MX73rlqeRSvGbtFzbkAue8v7Fx1+MltPAnz0sfQLGBmlDK69rM94h26whRyhxgbPFywh GyASR0C90FSh3QnXIlCi+Tk0GtiE1ZREJYArfa42IyrLBAaSOp1OPvOvqPwj4ye57em5 HA8g== X-Gm-Message-State: AOPr4FWCtoI94x4hRdx9vSpQnq/GL7XnPU5s70uYBoht+hj5eNZl5T6rOkzYCWNd9NbyXJb6Dmdm6vBkBQDBaw== MIME-Version: 1.0 X-Received: by 10.129.86.131 with SMTP id k125mr18415906ywb.158.1461520146901; Sun, 24 Apr 2016 10:49:06 -0700 (PDT) Received: by 10.129.109.67 with HTTP; Sun, 24 Apr 2016 10:49:06 -0700 (PDT) X-Originating-IP: [109.159.6.57] In-Reply-To: <015001d19e48$eead8c40$cc08a4c0$@belski.net> References: <06ac01d194e9$38fe0f40$aafa2dc0$@php.net> <048801d19d8a$e655b7c0$b3012740$@belski.net> <015001d19e48$eead8c40$cc08a4c0$@belski.net> Date: Sun, 24 Apr 2016 18:49:06 +0100 Message-ID: To: Anatol Belski Cc: Pierre Joye , Davey Shafik , Julien Pauli , Scott Arciszewski , Anatol Belski , PHP internals , Ferenc Kovacs , Stanislav Malyshev Content-Type: multipart/alternative; boundary=001a1143312c30615305313ead9c Subject: Re: [PHP-DEV] PHP 7.1 roadmap From: pthreads@pthreads.org (Joe Watkins) --001a1143312c30615305313ead9c Content-Type: text/plain; charset=UTF-8 Hi Anatol, Sounds good to me. Cheers Joe On Sun, Apr 24, 2016 at 5:47 PM, Anatol Belski wrote: > Hi, > > > -----Original Message----- > > From: Pierre Joye [mailto:pierre.php@gmail.com] > > Sent: Sunday, April 24, 2016 11:46 AM > > To: Davey Shafik > > Cc: Anatol Belski ; Julien Pauli ; > Scott > > Arciszewski ; Anatol Belski ; PHP > > internals ; Ferenc Kovacs ; > > Stanislav Malyshev > > Subject: Re: [PHP-DEV] PHP 7.1 roadmap > > > > > I'm honestly not 100% sure what all is involved, is this documented > > > somewhere? > > > > > > I'm a bit worried that my lack of C mastery will be an issue, but if > > > that's not a problem, then I'd be glad to move forward as you say > above. > > > > C knowledge is not required but a good thing. > > > > Also C knowledge is required to know the impact of a patch internally. > > Enough people are around to actually review patches and raises possible > issues. > > I would not worry too much about that. Lukas for example did a great job > and > > was not a C developer to begin with. > > > > The key role however of the RM is to ensure that the release process goes > > smoothly, the planing is respected and BC is kept during the full life > of a given > > release. > > > Yeah, good description. > > Davey, Joe, looks like we have a team now! I've already created the > https://wiki.php.net/todo/php71 . Added myself as well, similarly to > todo70, so we have more chance to have one team to be selected. I'd be > waiting yet till Tuesday and send the voting invitation. After the one week > vote (as per RFC), we'll be super good in time for planning and > preparations. > > Thanks > > Anatol > > --001a1143312c30615305313ead9c--