Thanks James! Most of it is on the wiki, and is pretty straightforward: Not surprisingly, I made OS X (almost) the same as iOS in structure as well: http://wiki.apache.org/cordova/IOSReleaseChecklist Some of the task should be covered in the JIRA issues generated I think.
On Tue, Jun 18, 2013 at 10:30 AM, James Jong <wjamesj...@gmail.com> wrote: > Shaz, I haven't done it before but I'll be happy to work with you and help > when you're out for iOS & OS X. FYI for planning, I will be out & away on > vacation June 26-July 15. > -James Jong > > On Jun 18, 2013, at 1:18 PM, Andrew Grieve <agri...@chromium.org> wrote: > > > Okay, created a new release bug & sub-tasks here: > > https://issues.apache.org/jira/browse/CB-3906 > > > > If you want to own a component, just assign it to yourself. > > > > > > On Tue, Jun 18, 2013 at 12:33 PM, Shazron <shaz...@gmail.com> wrote: > > > >> Echoing Fil here. I am the 'lead' for iOS and OS X but anyone can take > over > >> if they wish. What I'm interested in is who should be the "second" in > case > >> I can't do it (for example I am away almost all of August). Technically > >> anyone can take over but it will be nice if they are up to speed and > have > >> the necessary environment to test as a 'second'.. > >> > >> > >> > >> On Tue, Jun 18, 2013 at 9:04 AM, Filip Maj <f...@adobe.com> wrote: > >> > >>> 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" <cmarc...@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. > >>> > >>> > >> > >
