Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86025
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.48 as permitted sender)
MIME-Version: 1.0
Sender: julienpauli@gmail.com
In-Reply-To: <0375e734ddffc4f1590d9f91a616d5f8.squirrel@webmail.klapt.com>
References: <CAPwsocFSxCkizDjf4RKwJn4jvNjdHjoDqUsu=78hAcquEqddTg@mail.gmail.com>
 <CAH-PCH7RhVnjJrZFgT_jiW0fiyBaZBEEf1HHHCL-CE=BYFHm7A@mail.gmail.com>
 <CAEZPtU6XNMgzD+OaLJQKXJZ3Ee3W3Gqu_GcCOyd_gVAXJODDvw@mail.gmail.com>
 <CAH-PCH4QciKVcXdKK7Gi=gcXfkKP5Qm=gkhPc9cmFiEXJSh7MQ@mail.gmail.com>
 <fda29389de21ba26e708e9792f1c6ce6.squirrel@webmail.klapt.com>
 <CAH-PCH4L99QK3vZsB9Mf6Y=BBFpXWcO-dgi3cxvY4hn9yuiL7A@mail.gmail.com> <0375e734ddffc4f1590d9f91a616d5f8.squirrel@webmail.klapt.com>
Date: Wed, 29 Apr 2015 17:50:28 +0200
Message-ID: <CAMUwpuSXFheZbSXsE3yHevHAg+-_r0FAPbHkfNQ3HAYaDEJ4jg@mail.gmail.com>
To: Anatol Belski <anatol.php@belski.net>
Cc: Ferenc Kovacs <tyrael@php.net>, Pierre Joye <pierre.php@gmail.com>, Leigh <leight@gmail.com>, 
	PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d043bdf2a9bd0460514def298
Subject: Re: [PHP-DEV] 7.0 Release Management
From: jpauli@php.net (Julien Pauli)

--f46d043bdf2a9bd0460514def298
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 29, 2015 at 3:57 PM, Anatol Belski <anatol.php@belski.net>
wrote:

> On Wed, April 29, 2015 15:35, Ferenc Kovacs wrote:
> > On Wed, Apr 29, 2015 at 3:21 PM, Anatol Belski <anatol.php@belski.net>
> > 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... ;-)


Julien.Pauli

--f46d043bdf2a9bd0460514def298--