Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:86045 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 45917 invoked from network); 30 Apr 2015 00:08:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Apr 2015 00:08:58 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.42 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.192.42 mail-qg0-f42.google.com Received: from [209.85.192.42] ([209.85.192.42:33793] helo=mail-qg0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F4/53-29050-69271455 for ; Wed, 29 Apr 2015 20:08:55 -0400 Received: by qgfi89 with SMTP id i89so18598427qgf.1 for ; Wed, 29 Apr 2015 17:08:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=q/SbM/uVCuKrNiXVzGCQhQGC0eA0QI8f9nHi7bOYGw4=; b=Udh39tdx6UdU1glPEffbkmvCYE3y4Z0of1LiDM6b0PvDzv/RtwjkQZUt1OMBjMr015 U8ddzGTUdvdLbPYIfnKekw/WaPDhrgDHMJFg6K58nw+fKEB++0OYmPaRaCj6I2PrXsAS md4ounnLubOgSLwkQlvEwJ1hVuFLl+NvAWvi2c4R5HlciRcV91bvQ5RdWUZ62mRhwStG /VmelcKuF8VuF1sCXEk2je3B/svDrkkXkVrWecS5PMAeqt1NZmtrSPSPIXq1bRXvg+Pb rSqb91IjWGV6b9nd3J3dWEws0vmy7HG3izMqsMDV8mQB3dpeB2Nxu2g/hSZa8HBFjFNs 62ww== MIME-Version: 1.0 X-Received: by 10.55.19.160 with SMTP id 32mr3022515qkt.24.1430352532475; Wed, 29 Apr 2015 17:08:52 -0700 (PDT) Received: by 10.96.127.166 with HTTP; Wed, 29 Apr 2015 17:08:52 -0700 (PDT) In-Reply-To: References: <0375e734ddffc4f1590d9f91a616d5f8.squirrel@webmail.klapt.com> Date: Thu, 30 Apr 2015 07:08:52 +0700 Message-ID: To: Julien Pauli Cc: Anatol Belski , Ferenc Kovacs , Leigh , PHP Internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] 7.0 Release Management From: pierre.php@gmail.com (Pierre Joye) hi Julien. On Wed, Apr 29, 2015 at 10:50 PM, Julien Pauli wrote: > On Wed, Apr 29, 2015 at 3:57 PM, Anatol Belski > wrote: >> >> On Wed, April 29, 2015 15:35, Ferenc Kovacs wrote: >> > On Wed, Apr 29, 2015 at 3:21 PM, Anatol Belski >> > wrote: >> > >> > >> >> Hi, >> >> >> >> >> >> On Sun, April 5, 2015 09:05, Ferenc Kovacs wrote: >> >> >> >>> bumping the thread as we should start the release steps (branching >> >>> out 7.0, >> >>> tagging the first alpha or more likely beta) if we wanna keep up with >> >>> https://wiki.php.net/rfc/php7timeline >> >>> >> >>> >> >> after the recent discussion on IRC I would like to express the rediness >> >> to take on this job. As Kalle is willing to take this role as well, >> >> it'd >> >> probably make sense to hear what everyone thinks about my proposition. >> >> Possibly it could come to an election then. >> >> >> >> >> >> I guess this thread conjuncts with the "PHP7 RM" one started last year >> >> by Kalle. >> >> >> >> >> >> Regards >> >> >> >> >> >> Anatol >> >> >> >> >> > >> > Thanks for volunteering, albeit I wish you could have spoken a bit >> > sooner, so we avoid the awkward situation. I just wanted to repeat that >> > I >> > previously noted that based on my personal experience with 5.6, I think >> > that having two full time RMs for a major version would be much better. >> > Now >> > that we have two volunteers maybe we could also consider having both of >> > you guys and ofc. I can help with my experience on the RMing and the >> > process. >> > >> Yeah, actually I didn't think about RMing before. Thus my self-nomination >> is based on the discussion arguments that my participation could be >> convenient. Hence so late. With respect to your and others experience, >> that's why I'm asking. >> >> The suggestion for Kalle and me both doing the job - wouldn't we all three >> then jump over each others heads? Or one could part the tasks so we do it >> more or less independently (there are sure enough tasks)? Asking as I >> curretly have a minimal sights of the process, so not quite clear how it >> would go. > > > Na :-) > > I'm glad you both volunteer for RMing. > > Usually, only one guy does all the job, it is better and prevents one > jumping onto the other guy's head. > > But, Sometimes one may be so busy - or have personnal issues - that then it > is the second RM that comes over scene and does the job. > That's why we are two usually, one "master RM" that does the job, and one > "secondary RM" that comes to scene when "master RM" has some problems, or if > "master RM" wonders if it is good to do this or that (then RMs discuss each > other and take decision). > > But obviously, you two can change that process. > You can work together at the same time, splitting tasks to do, the only > thing is you have to be able to work together smoothly , but as we all are > OSS contributors, I guess we all are able to handle that. > > > Also, keep in mind that the release process is REALLY heavy before the GA , > and not that heavy once the GA is launched. > Preparing Alphas, betas, RCs, NEWS file, UPGRADING, checking for the doc to > be synced .... are hard jobs that take place before the GA, and can take a > lot of time. > In such period (that is : before the GA), it is usually really better to > have two brains and two pairs of hands to do the job. > > After the GA, don't worry too much, only security issues or BC breaks are to > be followed and taken care of, all the other tasks are easy to perform. > > Also, keep in mind that previous RMs, such as Ferenc or myself , can help > you in doing such tasks, feel free to ask, ping, mail, etc... ;-) Exactly, why we tried to always have an experienced RM working together with a new one, one of them has to have very good core knowledge (make the whole patch review easier). If anything and to keep the 2 RMs part, I am all for Ferenc and Anatol, a dream RMs team for 7. -- Pierre @pierrejoye | http://www.libgd.org