You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Andrew Grieve <ag...@chromium.org> on 2014/03/13 16:13:31 UTC

Release Managers

I'd previously brought up the idea of "Release Masters", and now after the
recent highlight of our release process by other Apache project members,
I've learned that they are common, and are actually called "Release
Managers".

Their role, in a nutshell, is to take ownership of a release (either
through delegation, or by doing it themselves).

It's generally not a glorious job, so it would be great if we could do a
bit of a rotation on it:
- a rotation for tools,
- a rotation for plugins,
- a rotation for platforms release.

For tools & plugins, the responsibility is a bit better defined I think -
they are responsible for going through the steps in the release process.

For platform releases, the release manager wouldn't necessarily be
responsible for individual platforms, but rather for things like docs,
website, dist/, and for poking people.


As for a rotation, one thought is to write down the names of those willing
in the actual release steps .md files, and then they can plan out how to
schedule themselves from there.

How does this sound?

RE: Release Managers

Posted by "Dao, Thomas" <Th...@T-Mobile.com>.
Sounds good.  Please add me to the rotation.  I can probable start with tools and plugins.  Thanks

Thomas


-----Original Message-----
From: agrieve@google.com [mailto:agrieve@google.com] On Behalf Of Andrew Grieve
Sent: Thursday, March 13, 2014 8:14 AM
To: dev
Subject: Release Managers

I'd previously brought up the idea of "Release Masters", and now after the recent highlight of our release process by other Apache project members, I've learned that they are common, and are actually called "Release Managers".

Their role, in a nutshell, is to take ownership of a release (either through delegation, or by doing it themselves).

It's generally not a glorious job, so it would be great if we could do a bit of a rotation on it:
- a rotation for tools,
- a rotation for plugins,
- a rotation for platforms release.

For tools & plugins, the responsibility is a bit better defined I think - they are responsible for going through the steps in the release process.

For platform releases, the release manager wouldn't necessarily be responsible for individual platforms, but rather for things like docs, website, dist/, and for poking people.


As for a rotation, one thought is to write down the names of those willing in the actual release steps .md files, and then they can plan out how to schedule themselves from there.

How does this sound?

Re: Release Managers

Posted by Shazron <sh...@gmail.com>.
+1 maybe a Release Training hangout


On Thu, Mar 13, 2014 at 1:19 PM, Brian LeRoux <b...@brian.io> wrote:

> Ya I'm into it. I think a buddy system would be good. Steve could pair to
> get this started and 'train the trainers'.
>
>
> On Thu, Mar 13, 2014 at 12:16 PM, Braden Shepherdson <braden@chromium.org
> >wrote:
>
> > +1 to this concept.
> >
> > I'm in to manage the tools releases, not familiar at all with the process
> > for the others. But I'm willing to learn enough to do it, if we're just
> > passing these responsibilities around.
> >
> > Braden
> >
> >
> > On Thu, Mar 13, 2014 at 2:10 PM, Marcel Kinard <cm...@gmail.com>
> wrote:
> >
> > > +1, I'm throwing my hat in the ring.
> > >
> > > On Mar 13, 2014, at 1:34 PM, Bryan Higgins <br...@bryanhiggins.net>
> > wrote:
> > >
> > > > +1, I'll throw my hat in the ring as well
> > >
> > >
> >
>

Re: Release Managers

Posted by Brian LeRoux <b...@brian.io>.
Ya I'm into it. I think a buddy system would be good. Steve could pair to
get this started and 'train the trainers'.


On Thu, Mar 13, 2014 at 12:16 PM, Braden Shepherdson <br...@chromium.org>wrote:

> +1 to this concept.
>
> I'm in to manage the tools releases, not familiar at all with the process
> for the others. But I'm willing to learn enough to do it, if we're just
> passing these responsibilities around.
>
> Braden
>
>
> On Thu, Mar 13, 2014 at 2:10 PM, Marcel Kinard <cm...@gmail.com> wrote:
>
> > +1, I'm throwing my hat in the ring.
> >
> > On Mar 13, 2014, at 1:34 PM, Bryan Higgins <br...@bryanhiggins.net>
> wrote:
> >
> > > +1, I'll throw my hat in the ring as well
> >
> >
>

Re: Release Managers

Posted by James Jong <wj...@gmail.com>.
+1 Would be great to spread the knowledge around.
-James Jong

On Mar 13, 2014, at 3:16 PM, Braden Shepherdson <br...@chromium.org> wrote:

> +1 to this concept.
> 
> I'm in to manage the tools releases, not familiar at all with the process
> for the others. But I'm willing to learn enough to do it, if we're just
> passing these responsibilities around.
> 
> Braden
> 
> 
> On Thu, Mar 13, 2014 at 2:10 PM, Marcel Kinard <cm...@gmail.com> wrote:
> 
>> +1, I'm throwing my hat in the ring.
>> 
>> On Mar 13, 2014, at 1:34 PM, Bryan Higgins <br...@bryanhiggins.net> wrote:
>> 
>>> +1, I'll throw my hat in the ring as well
>> 
>> 


Re: Release Managers

Posted by Braden Shepherdson <br...@chromium.org>.
+1 to this concept.

I'm in to manage the tools releases, not familiar at all with the process
for the others. But I'm willing to learn enough to do it, if we're just
passing these responsibilities around.

Braden


On Thu, Mar 13, 2014 at 2:10 PM, Marcel Kinard <cm...@gmail.com> wrote:

> +1, I'm throwing my hat in the ring.
>
> On Mar 13, 2014, at 1:34 PM, Bryan Higgins <br...@bryanhiggins.net> wrote:
>
> > +1, I'll throw my hat in the ring as well
>
>

Re: Release Managers

Posted by Marcel Kinard <cm...@gmail.com>.
+1, I'm throwing my hat in the ring.

On Mar 13, 2014, at 1:34 PM, Bryan Higgins <br...@bryanhiggins.net> wrote:

> +1, I'll throw my hat in the ring as well


Re: Release Managers

Posted by Bryan Higgins <br...@bryanhiggins.net>.
+1, I'll throw my hat in the ring as well


On Thu, Mar 13, 2014 at 1:13 PM, Steven Gill <st...@gmail.com> wrote:

> I'm obviously a +1 and highly support this idea.
> On Mar 13, 2014 9:57 AM, "Naik, Archana" <na...@lab126.com> wrote:
>
> > +1 I like the idea too. I have never done a release and don't mind being
> a
> > guinea pig hereŠ :)
> >
> > Archana
> >
> > On 3/13/14 9:44 AM, "Michal Mocny" <mm...@chromium.org> wrote:
> >
> > >+1, like the idea of putting your name into a hat.
> > >
> > >How about "coaching" the first time someone does a release?  Do we
> prefer
> > >to let the docs stand for themselves?
> > >
> > >-Michal
> > >
> > >
> > >On Thu, Mar 13, 2014 at 11:13 AM, Andrew Grieve
> > ><ag...@chromium.org>wrote:
> > >
> > >> I'd previously brought up the idea of "Release Masters", and now after
> > >>the
> > >> recent highlight of our release process by other Apache project
> members,
> > >> I've learned that they are common, and are actually called "Release
> > >> Managers".
> > >>
> > >> Their role, in a nutshell, is to take ownership of a release (either
> > >> through delegation, or by doing it themselves).
> > >>
> > >> It's generally not a glorious job, so it would be great if we could
> do a
> > >> bit of a rotation on it:
> > >> - a rotation for tools,
> > >> - a rotation for plugins,
> > >> - a rotation for platforms release.
> > >>
> > >> For tools & plugins, the responsibility is a bit better defined I
> think
> > >>-
> > >> they are responsible for going through the steps in the release
> process.
> > >>
> > >> For platform releases, the release manager wouldn't necessarily be
> > >> responsible for individual platforms, but rather for things like docs,
> > >> website, dist/, and for poking people.
> > >>
> > >>
> > >> As for a rotation, one thought is to write down the names of those
> > >>willing
> > >> in the actual release steps .md files, and then they can plan out how
> to
> > >> schedule themselves from there.
> > >>
> > >> How does this sound?
> > >>
> >
> >
>

Re: Release Managers

Posted by Steven Gill <st...@gmail.com>.
I'm obviously a +1 and highly support this idea.
On Mar 13, 2014 9:57 AM, "Naik, Archana" <na...@lab126.com> wrote:

> +1 I like the idea too. I have never done a release and don't mind being a
> guinea pig hereŠ :)
>
> Archana
>
> On 3/13/14 9:44 AM, "Michal Mocny" <mm...@chromium.org> wrote:
>
> >+1, like the idea of putting your name into a hat.
> >
> >How about "coaching" the first time someone does a release?  Do we prefer
> >to let the docs stand for themselves?
> >
> >-Michal
> >
> >
> >On Thu, Mar 13, 2014 at 11:13 AM, Andrew Grieve
> ><ag...@chromium.org>wrote:
> >
> >> I'd previously brought up the idea of "Release Masters", and now after
> >>the
> >> recent highlight of our release process by other Apache project members,
> >> I've learned that they are common, and are actually called "Release
> >> Managers".
> >>
> >> Their role, in a nutshell, is to take ownership of a release (either
> >> through delegation, or by doing it themselves).
> >>
> >> It's generally not a glorious job, so it would be great if we could do a
> >> bit of a rotation on it:
> >> - a rotation for tools,
> >> - a rotation for plugins,
> >> - a rotation for platforms release.
> >>
> >> For tools & plugins, the responsibility is a bit better defined I think
> >>-
> >> they are responsible for going through the steps in the release process.
> >>
> >> For platform releases, the release manager wouldn't necessarily be
> >> responsible for individual platforms, but rather for things like docs,
> >> website, dist/, and for poking people.
> >>
> >>
> >> As for a rotation, one thought is to write down the names of those
> >>willing
> >> in the actual release steps .md files, and then they can plan out how to
> >> schedule themselves from there.
> >>
> >> How does this sound?
> >>
>
>

Re: Release Managers

Posted by "Naik, Archana" <na...@lab126.com>.
+1 I like the idea too. I have never done a release and don't mind being a
guinea pig hereŠ :)

Archana

On 3/13/14 9:44 AM, "Michal Mocny" <mm...@chromium.org> wrote:

>+1, like the idea of putting your name into a hat.
>
>How about "coaching" the first time someone does a release?  Do we prefer
>to let the docs stand for themselves?
>
>-Michal
>
>
>On Thu, Mar 13, 2014 at 11:13 AM, Andrew Grieve
><ag...@chromium.org>wrote:
>
>> I'd previously brought up the idea of "Release Masters", and now after
>>the
>> recent highlight of our release process by other Apache project members,
>> I've learned that they are common, and are actually called "Release
>> Managers".
>>
>> Their role, in a nutshell, is to take ownership of a release (either
>> through delegation, or by doing it themselves).
>>
>> It's generally not a glorious job, so it would be great if we could do a
>> bit of a rotation on it:
>> - a rotation for tools,
>> - a rotation for plugins,
>> - a rotation for platforms release.
>>
>> For tools & plugins, the responsibility is a bit better defined I think
>>-
>> they are responsible for going through the steps in the release process.
>>
>> For platform releases, the release manager wouldn't necessarily be
>> responsible for individual platforms, but rather for things like docs,
>> website, dist/, and for poking people.
>>
>>
>> As for a rotation, one thought is to write down the names of those
>>willing
>> in the actual release steps .md files, and then they can plan out how to
>> schedule themselves from there.
>>
>> How does this sound?
>>


RE: Release Managers

Posted by "Parashuram Narasimhan (MS OPEN TECH)" <pa...@microsoft.com>.
Is there a place where the volunteers and noted with possible release schedules? Or do we just volunteer for the upcoming release and get picked at random?  

-----Original Message-----
From: Lorin Beer [mailto:lorin.beer.dev@gmail.com] 
Sent: Monday, March 17, 2014 9:44 AM
To: dev
Subject: Re: Release Managers

+1 + i


On Mon, Mar 17, 2014 at 7:37 AM, Ian Clelland <ic...@chromium.org>wrote:

> +1, this is a good idea.
>
>
> On Thu, Mar 13, 2014 at 12:44 PM, Michal Mocny <mm...@chromium.org>
> wrote:
>
> > +1, like the idea of putting your name into a hat.
> >
> > How about "coaching" the first time someone does a release?  Do we 
> > prefer to let the docs stand for themselves?
> >
>
> Coaching is definitely a good idea as well; or something like it. 
> However, making sure that the docs are up to date and usable should be 
> an important part of being RM.
>
> It should't be an onerous thing -- just "if there's a step missing, or 
> something that wouldn't have worked, then fix the docs for the next guy".
>
> Ian
>
>
> >
> > -Michal
> >
> >
> > On Thu, Mar 13, 2014 at 11:13 AM, Andrew Grieve 
> > <agrieve@chromium.org
> > >wrote:
> >
> > > I'd previously brought up the idea of "Release Masters", and now 
> > > after
> > the
> > > recent highlight of our release process by other Apache project
> members,
> > > I've learned that they are common, and are actually called 
> > > "Release Managers".
> > >
> > > Their role, in a nutshell, is to take ownership of a release 
> > > (either through delegation, or by doing it themselves).
> > >
> > > It's generally not a glorious job, so it would be great if we 
> > > could do
> a
> > > bit of a rotation on it:
> > > - a rotation for tools,
> > > - a rotation for plugins,
> > > - a rotation for platforms release.
> > >
> > > For tools & plugins, the responsibility is a bit better defined I
> think -
> > > they are responsible for going through the steps in the release
> process.
> > >
> > > For platform releases, the release manager wouldn't necessarily be 
> > > responsible for individual platforms, but rather for things like 
> > > docs, website, dist/, and for poking people.
> > >
> > >
> > > As for a rotation, one thought is to write down the names of those
> > willing
> > > in the actual release steps .md files, and then they can plan out 
> > > how
> to
> > > schedule themselves from there.
> > >
> > > How does this sound?
> > >
> >
>

Re: Release Managers

Posted by Lorin Beer <lo...@gmail.com>.
+1 + i


On Mon, Mar 17, 2014 at 7:37 AM, Ian Clelland <ic...@chromium.org>wrote:

> +1, this is a good idea.
>
>
> On Thu, Mar 13, 2014 at 12:44 PM, Michal Mocny <mm...@chromium.org>
> wrote:
>
> > +1, like the idea of putting your name into a hat.
> >
> > How about "coaching" the first time someone does a release?  Do we prefer
> > to let the docs stand for themselves?
> >
>
> Coaching is definitely a good idea as well; or something like it. However,
> making sure that the docs are up to date and usable should be an important
> part of being RM.
>
> It should't be an onerous thing -- just "if there's a step missing, or
> something that wouldn't have worked, then fix the docs for the next guy".
>
> Ian
>
>
> >
> > -Michal
> >
> >
> > On Thu, Mar 13, 2014 at 11:13 AM, Andrew Grieve <agrieve@chromium.org
> > >wrote:
> >
> > > I'd previously brought up the idea of "Release Masters", and now after
> > the
> > > recent highlight of our release process by other Apache project
> members,
> > > I've learned that they are common, and are actually called "Release
> > > Managers".
> > >
> > > Their role, in a nutshell, is to take ownership of a release (either
> > > through delegation, or by doing it themselves).
> > >
> > > It's generally not a glorious job, so it would be great if we could do
> a
> > > bit of a rotation on it:
> > > - a rotation for tools,
> > > - a rotation for plugins,
> > > - a rotation for platforms release.
> > >
> > > For tools & plugins, the responsibility is a bit better defined I
> think -
> > > they are responsible for going through the steps in the release
> process.
> > >
> > > For platform releases, the release manager wouldn't necessarily be
> > > responsible for individual platforms, but rather for things like docs,
> > > website, dist/, and for poking people.
> > >
> > >
> > > As for a rotation, one thought is to write down the names of those
> > willing
> > > in the actual release steps .md files, and then they can plan out how
> to
> > > schedule themselves from there.
> > >
> > > How does this sound?
> > >
> >
>

Re: Release Managers

Posted by Ian Clelland <ic...@chromium.org>.
+1, this is a good idea.


On Thu, Mar 13, 2014 at 12:44 PM, Michal Mocny <mm...@chromium.org> wrote:

> +1, like the idea of putting your name into a hat.
>
> How about "coaching" the first time someone does a release?  Do we prefer
> to let the docs stand for themselves?
>

Coaching is definitely a good idea as well; or something like it. However,
making sure that the docs are up to date and usable should be an important
part of being RM.

It should't be an onerous thing -- just "if there's a step missing, or
something that wouldn't have worked, then fix the docs for the next guy".

Ian


>
> -Michal
>
>
> On Thu, Mar 13, 2014 at 11:13 AM, Andrew Grieve <agrieve@chromium.org
> >wrote:
>
> > I'd previously brought up the idea of "Release Masters", and now after
> the
> > recent highlight of our release process by other Apache project members,
> > I've learned that they are common, and are actually called "Release
> > Managers".
> >
> > Their role, in a nutshell, is to take ownership of a release (either
> > through delegation, or by doing it themselves).
> >
> > It's generally not a glorious job, so it would be great if we could do a
> > bit of a rotation on it:
> > - a rotation for tools,
> > - a rotation for plugins,
> > - a rotation for platforms release.
> >
> > For tools & plugins, the responsibility is a bit better defined I think -
> > they are responsible for going through the steps in the release process.
> >
> > For platform releases, the release manager wouldn't necessarily be
> > responsible for individual platforms, but rather for things like docs,
> > website, dist/, and for poking people.
> >
> >
> > As for a rotation, one thought is to write down the names of those
> willing
> > in the actual release steps .md files, and then they can plan out how to
> > schedule themselves from there.
> >
> > How does this sound?
> >
>

Re: Release Managers

Posted by Michal Mocny <mm...@chromium.org>.
+1, like the idea of putting your name into a hat.

How about "coaching" the first time someone does a release?  Do we prefer
to let the docs stand for themselves?

-Michal


On Thu, Mar 13, 2014 at 11:13 AM, Andrew Grieve <ag...@chromium.org>wrote:

> I'd previously brought up the idea of "Release Masters", and now after the
> recent highlight of our release process by other Apache project members,
> I've learned that they are common, and are actually called "Release
> Managers".
>
> Their role, in a nutshell, is to take ownership of a release (either
> through delegation, or by doing it themselves).
>
> It's generally not a glorious job, so it would be great if we could do a
> bit of a rotation on it:
> - a rotation for tools,
> - a rotation for plugins,
> - a rotation for platforms release.
>
> For tools & plugins, the responsibility is a bit better defined I think -
> they are responsible for going through the steps in the release process.
>
> For platform releases, the release manager wouldn't necessarily be
> responsible for individual platforms, but rather for things like docs,
> website, dist/, and for poking people.
>
>
> As for a rotation, one thought is to write down the names of those willing
> in the actual release steps .md files, and then they can plan out how to
> schedule themselves from there.
>
> How does this sound?
>