cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michal Mocny <mmo...@chromium.org>
Subject Re: Release Masters & Component Leads
Date Tue, 03 Sep 2013 17:31:46 GMT
Volunteer maps well to hows its been done implicitly.  If you cannot take a
given week, find a sensible replacement.

Rotation among willing folks makes some sense in terms of passing down of
knowledge.

-Michal


On Tue, Sep 3, 2013 at 12:51 PM, Andrew Grieve <agrieve@chromium.org> wrote:

> I brought up this idea before (http://markmail.org/thread/75fv4ru7rd4vwrrb
> ),
> it was well received I think, but never made its way to our CuttingReleases
> page. I'd like to move forward with formally introducing this concept on
> our wiki page.
>
>
> Component Lead:
> - For each release, each repo has a Component Lead
> - They perform release steps and signs off on a component (ios, android,
> etc).
>
> Release Master:
> - Delegate release tasks
> - Communicate release status
> - Nag people responsible for unfinished tasks
>
> >
> Sound good?
>
>
> Motivation behind making a single person the "release master" for a
> release:
>  - To ensure that steps actually get done by ensuring each task has an
> owner
>  - Improve coordination & communication during releases
>
> Before I go and add this to the release wiki pages though:
> - What should the process be for choosing the release master / component
> lead?
>     - Have a rotation?
>     - Ask for volunteer each time?
>
>
> Any other thoughts along the matter?
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message