Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of fil@adobe.com designates
 64.18.1.23 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Date: Tue, 18 Jun 2013 09:04:46 -0700
Subject: Re: Release Masters?
Thread-Topic: Release Masters?
Thread-Index: Ac5sPZAUE7QTkXf6RIuNFhcHDc+ojA==
Message-ID: <CDE5D2F9.20E45%fil@adobe.com>
In-Reply-To: <F11B11EE-AB0A-4C39-BC1A-352604C54C99@gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.5.130515
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

I am the "lead" for cordova-js in JIRA that anyone else can take over if
they wish. My focus is more on the tooling nowadays. Lots of
features/improvements/wishes in that component..

On 6/18/13 9:02 AM, "Marcel Kinard" <cmarcelk@gmail.com> wrote:

>On Jun 18, 2013, at 5:07 AM, Brian LeRoux <b@brian.io> wrote:
>
>> Think we already have this as per the issue tracker concept of 'leads'
>> but I do agree formalizing the role a little more would help.
>
>Do all the components leads (as listed in Jira) want to be release
>masters for their components? If not, James Jong and I could probably own
>the "release master" role for a component each, in case any one is
>looking to unload that.