cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nikhil Khandelwal <nikhi...@microsoft.com>
Subject RE: [DISCUSS] Jira triage
Date Tue, 27 Oct 2015 17:26:07 GMT
I made some updates based on feedback. Please review this version: https://github.com/apache/cordova-coho/pull/97

I'm hoping we can agree on a JIRA triage process in the next couple of days.

-Nikhil

-----Original Message-----
From: Joe Bowser [mailto:bowserj@gmail.com] 
Sent: Tuesday, October 20, 2015 9:24 AM
To: dev <dev@cordova.apache.org>
Subject: Re: [DISCUSS] Jira triage

I've added my feedback at the pull request.  I do think that 2 days is too soon to close something,
since I can close almost all the current issues on JIRA if that was the case.

On Tue, Oct 20, 2015 at 9:12 AM, Nikhil Khandelwal <nikhilkh@microsoft.com>
wrote:

> I am fine with all these recommendations. The key is to be consistent. 
> I have documented this and more details here:
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithu
> b.com%2fapache%2fcordova-coho%2fpull%2f97&data=01%7c01%7cnikhilkh%40mi
> crosoft.com%7c234742a2be054f60290708d2d96af314%7c72f988bf86f141af91ab2
> d7cd011db47%7c1&sdata=FV7OkZ85gneTNfrSPYmWAZvZjWkO%2bPTmPGYThsuqAkI%3d
>
> Let's continue discussion on the PR or this thread. I don't want the 
> process to be heavy-weight - though my goal is to address few key things:
> - Consistent process for JIRA triage
> - Accountability for who does JIRA triage? Is it component owner or a 
> rotating duty appropriate for a tech lead? Either way this is a fair 
> amount of work - but absolutely important for maintaining high level of quality.
> - We identify and raise critical regressions and release patch 
> versions to fix them. I think we need to respond faster to higher pri issues.
>
> -Nikhil
>
> -----Original Message-----
> From: Shazron [mailto:shazron@gmail.com]
> Sent: Monday, October 19, 2015 12:11 PM
> To: dev@cordova.apache.org
> Subject: Re: [DISCUSS] Jira triage
>
> Thanks Steve.
> Three recommendations below.
>
> A.
> I recommend a "Platform" pre-fix for platform issues. ie rename "iOS", 
> "Android" etc to "Platform iOS", "Platform Android" (like plugins have 
> a prefix of "Plugin" already).
>
> This however would not prevent people from assigning these components 
> to non-platform issues however :/ So it will be up to us to triage it 
> appropriately.
>
> I've been treating a "Component" as equivalent to filing an issue 
> against the appropriate repo (1:1 correspondence).
> This makes it easier to focus on a particular repo's issues without 
> the noise of unrelated plugin issues.
>
> B.
> For issues that are related to a platform implementation of a plugin, 
> my recommendation is to tag it with the component related to the 
> plugin, i.e "Plugin Contacts", then add a label for the platform 
> "ios". Currently I've been adding it to the Environment field, which may not be as searchable.
>
> So from our Cordova project search:
>
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissue
> s.apache.org%2fjira%2fissues%2f%3fjql%3dproject%2520%253D%2520CB&data=
> 01%7c01%7cnikhilkh%40microsoft.com%7c097b79948b2141e4ff7508d2d8b9393c%
> 7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=K%2bHGeNnNg400WtWEK4vYlHK
> CZzboEGVs1wC7LJoHR50%3d
>
> (maybe we can alias this to
> https://na01.safelinks.protection.outlook.com/?url=search.cordova.io%3
> f&data=01%7c01%7cnikhilkh%40microsoft.com%7c097b79948b2141e4ff7508d2d8
> b9393c%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=ufesrrJ81qVLwYL80a
> qMpEsWAU5QmagI6eHvuw88Vc4%3d
> )
>
> Add the Component - "Plugin Contacts"
> Add the Label - "ios".
>
> You'll get this result:
>
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissue
> s.apache.org%2fjira%2fissues%2f%3fjql%3dproject%2520%253D%2520CB%2520A
> ND%2520component%2520%253D%2520%2522Plugin%2520Contacts%2522%2520AND%2
> 520labels%2520%253D%2520ios&data=01%7c01%7cnikhilkh%40microsoft.com%7c
> 097b79948b2141e4ff7508d2d8b9393c%7c72f988bf86f141af91ab2d7cd011db47%7c
> 1&sdata=BN4b8GeohG%2bplE5Q2MXi6V%2bSv0mlgyDKI21dhiOV62g%3d
>
> C.
> One component per issue - hard rule. It can start out as a discussion 
> involving more than one Component, but MUST evolve into multiple 
> issues (or
> subtasks) -- one per component. I've seen issues where it affects 
> multiple components and the communication on what has been done for 
> what platform gets muddled, resulting in inaction for one platform.
>
>
> Shaz
>
> On Sat, Oct 17, 2015 at 10:53 PM, Steven Gill <stevengill97@gmail.com>
> wrote:
> > At the Cordova F2F, some discrepancies were found in how we are 
> > triaging issues on Jira. Especially in terms of plugin issues and if 
> > they should have platform related components. This email is to 
> > discuss the discrepancies and for recommendations to be made and agreed upon.
> >
> > According to the F2F minutes[1], Joe, Shaz and Nikhil would lead the 
> > discussion and make recommendations for the triage workflow. And of 
> > course, everyone is encouraged and welcomed to participate.
> >
> > [1]
> > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fdocs.
> > google.com%2fdocument%2fd%2f1MArKRmnLS052LBbhPxJF57_4ZivghOj8znWo5sT
> > Ck
> > bU%2fedit%3fusp%3dsharing&data=01%7c01%7cnikhilkh%40microsoft.com%7c
> > 09 
> > 7b79948b2141e4ff7508d2d8b9393c%7c72f988bf86f141af91ab2d7cd011db47%7c
> > 1& sdata=60eBbnJVRZEa4nHlxOMHmSsHn0I1saLnL4%2bgvuwqhnk%3d
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Mime
View raw message