You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Filip Maj <ma...@gmail.com> on 2017/07/22 19:30:17 UTC
Highlighting top issues w/ JIRA boards and labels
Hi everyone,
Over the past little while, I've been trying to wrap my head around
what open issues exist within Cordova, which ones are top priority +
how we can identify the most pressing issues, and how to bubble those
up to the top for PMC members and contributor/committers.
With some of the other Adobians, we've slapped together a few JIRA
boards that we think can help wrangle the 2,054+ unresolved issues in
JIRA [1]. The idea is to use two labels to differentiate between
issues identified as "we need to fix this for the next release" and
"we need to fix this at some point in the future."
One board is called the "Cordova Backlog" [2]. It shows open or in
progress issues for _all_ components / repos within Cordova that are
tagged with the 'backlog' label. I think this board helps to
identify/aggregate triaged issues that committers/PMC members feel are
important enough to address at some point - but not necessarily for
the next release. It also gives a nice high-level overview of Cordova
as a whole since it shows issues across all repos. To make an issue
show up in this board, simply add the 'backlog' label to a JIRA issue.
To complement this, and make working towards the next release for
particular components easier, we've added a set of boards we've called
"Next". These boards are per-component (or roughly, per group of
related components), and show open, in progress and completed issues.
The idea with these boards is to give specific repo maintainers +
contributors a shared todo list as they work towards nailing a
release. We already had a "cordova-next" board in the past which was
mainly used in prep for major version releases of the tooling - this
board has been renamed "tools-next." The specific boards created are:
- browser-next [3] for the cordova-browser platform
- docs-next [4] for cordova-docs
- plugins-next [5] for all cordova plugins
- android-next [6] for cordova-android
- tools-next [7] for all cordova tooling (cli, lib, fetch, create, etc.)
- ios-next [8] for cordova-ios
- windows-next [9] for cordova-windows
To make an issue show up in one of these, apply the relevant *-next
label to an issue, i.e. android-next, or docs-next, or browser-next.
The "release" link available on these boards could also be used to
help create changelogs.
So, to summarize:
- hoping this can create visibility and a shared backlog / work list
to help with collaboration between contributors
- hoping a consistent approach across repos can help increase
transparency and lower confusion as contributors work across repos
Open to any comments or questions! My goal with this is to try to
create a shared workflow for contributors, that is relatively
consistent across components, in order to increase ease of
collaboration - this is not set in stone, but rather a first stab, so
I am open to all ideas to try to make this more accessible for
everyone.
Cheers,
Fil
[1] https://issues.apache.org/jira/secure/ConfigureReport.jspa?filterid=12320364&mapper=components&selectedProjectId=12312420&reportKey=com.atlassian.jira.plugin.system.reports%3Asinglelevelgroupby&Next=Next
[2] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=195
[3] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=193
[4] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=198
[5] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=194
[6] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=190
[7] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=171
[8] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=192
[9] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=191
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: Highlighting top issues w/ JIRA boards and labels
Posted by Filip Maj <ma...@gmail.com>.
Thanks for tweaking your workflow Shaz.
FWIW I like the fixVersion field, and I don't think it's incompatible
with the backlog/*-next labels - feels like the two can live
side-by-side.
Taking a look at the board configuration, it looks like only those
blessed by Apache Infra to have JIRA Karma can create boards in the
first place (I think that right now is Steve, Shaz and me). As for
board detail, there is no 'description' field or some such, just Board
Name. So to your first issue, we could change the board name to better
reflect what they intend. Any preference to how to name them?
As for board permissions, the board creator can individually add users
to the admin list for the boards. Most of these boards are owned by
Steve right now (I own the docs-next board). It looks like JIRA can
also add "Groups" to the Board Admin list, but I don't see a cordova
dev-list or some such group. I'll try pinging INFRA to see if we can
have a group like cordova-pmc added or something along those lines. In
the mean time, I'll add Steve and Shaz to the admin list for the docs
and backlog boards.
On Sun, Jul 23, 2017 at 12:05 AM, Shazron <sh...@gmail.com> wrote:
> Thanks Fil!
> I like this organization and consistency (especially for getting new
> contributors up to speed).
>
> As an example, this is what I've done with my existing boards. I have 3:
> cordova-ios@4.4.1 (labelled ios-next, backlog)
> cordova-ios@4.5.0 (labelled backlog)
> cordova-ios@5.0.0 (labelled backlog)
>
> I will remove the first two boards (soon), knowing that I have captured
> them into this new workflow.
>
> -------------------------------
> cordova-ios@4.4.1 Board:
> ios-next board is for label ios-next only -- the next ios-version to be
> released is 4.4.1, thus those issues are labelled with ios-next.
> Once I am done with all the issues, I use the Release functionality of the
> board to say that cordova-ios@4.4.1 is a release.
> Currently also labelled with 'backlog', I will remove that label.
>
> cordova-ios@4.5.0 Board:
> labelled backlog so it shows in the backlog. The fix version currently is
> "cordova-ios@4.5.0" to indicate planned release.
> I will remove this Fix Version, and let it remain in the backlog so the
> next version can be ad-hoc and the version number for released would be
> according to semver.
>
> cordova-ios@5.0.0 Board:
> labelled backlog so it shows in the backlog. The fix version is
> "cordova-ios@5.0.0" to indicate planned release.
> This is planned because it should contain breaking changes (API change, iOS
> Support change etc). When the time comes, this will be labelled 'ios-next'
> since it also exists in the backlog. It still has a board for visibility
> (although it can be achieved with a saved filter).
> -------------------------------
>
> From the aftermath I will have only two boards:
> ios-next
> cordova-ios@5.0.0 (labelled backlog, fix-version cordova-ios@5.0.0)
>
> After an ios-next release:
> 1. I will triage the backlog for component: ios issues
> 2. Label items for the next release with "ios-next"
> 3. Remove the "backlog" label for these same items
>
> As new issues come in:
> 1. Triage them into "backlog" label OR
> 2. Triage them into "ios-next" label
>
> You move an item from the "backlog" to "ios-next (or vice-versa) by
> changing the label.
> Your issue should not have both labels.
>
> =========
> ISSUES:
> 1. Right now the 'ios-next' board is just named that, 'ios-next'. It is not
> clearly visible what the next planned version is. I'm not sure how to
> effectively communicate this in JIRA with the Kanban board interface. This
> information should ideally be on the Board itself.
> 2. We should add more Admins for these boards across the PMC
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Sat, Jul 22, 2017 at 12:30 PM, Filip Maj <ma...@gmail.com> wrote:
>
>> Hi everyone,
>>
>> Over the past little while, I've been trying to wrap my head around
>> what open issues exist within Cordova, which ones are top priority +
>> how we can identify the most pressing issues, and how to bubble those
>> up to the top for PMC members and contributor/committers.
>>
>> With some of the other Adobians, we've slapped together a few JIRA
>> boards that we think can help wrangle the 2,054+ unresolved issues in
>> JIRA [1]. The idea is to use two labels to differentiate between
>> issues identified as "we need to fix this for the next release" and
>> "we need to fix this at some point in the future."
>>
>> One board is called the "Cordova Backlog" [2]. It shows open or in
>> progress issues for _all_ components / repos within Cordova that are
>> tagged with the 'backlog' label. I think this board helps to
>> identify/aggregate triaged issues that committers/PMC members feel are
>> important enough to address at some point - but not necessarily for
>> the next release. It also gives a nice high-level overview of Cordova
>> as a whole since it shows issues across all repos. To make an issue
>> show up in this board, simply add the 'backlog' label to a JIRA issue.
>>
>> To complement this, and make working towards the next release for
>> particular components easier, we've added a set of boards we've called
>> "Next". These boards are per-component (or roughly, per group of
>> related components), and show open, in progress and completed issues.
>> The idea with these boards is to give specific repo maintainers +
>> contributors a shared todo list as they work towards nailing a
>> release. We already had a "cordova-next" board in the past which was
>> mainly used in prep for major version releases of the tooling - this
>> board has been renamed "tools-next." The specific boards created are:
>> - browser-next [3] for the cordova-browser platform
>> - docs-next [4] for cordova-docs
>> - plugins-next [5] for all cordova plugins
>> - android-next [6] for cordova-android
>> - tools-next [7] for all cordova tooling (cli, lib, fetch, create, etc.)
>> - ios-next [8] for cordova-ios
>> - windows-next [9] for cordova-windows
>>
>> To make an issue show up in one of these, apply the relevant *-next
>> label to an issue, i.e. android-next, or docs-next, or browser-next.
>> The "release" link available on these boards could also be used to
>> help create changelogs.
>>
>> So, to summarize:
>> - hoping this can create visibility and a shared backlog / work list
>> to help with collaboration between contributors
>> - hoping a consistent approach across repos can help increase
>> transparency and lower confusion as contributors work across repos
>>
>> Open to any comments or questions! My goal with this is to try to
>> create a shared workflow for contributors, that is relatively
>> consistent across components, in order to increase ease of
>> collaboration - this is not set in stone, but rather a first stab, so
>> I am open to all ideas to try to make this more accessible for
>> everyone.
>>
>> Cheers,
>> Fil
>>
>>
>> [1] https://issues.apache.org/jira/secure/ConfigureReport.
>> jspa?filterid=12320364&mapper=components&selectedProjectId=
>> 12312420&reportKey=com.atlassian.jira.plugin.system.
>> reports%3Asinglelevelgroupby&Next=Next
>> [2] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=195
>> [3] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=193
>> [4] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=198
>> [5] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=194
>> [6] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=190
>> [7] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=171
>> [8] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=192
>> [9] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=191
>>
>> ---------------------------------------------------------------------
>> 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
Re: Highlighting top issues w/ JIRA boards and labels
Posted by Shazron <sh...@gmail.com>.
Thanks Fil!
I like this organization and consistency (especially for getting new
contributors up to speed).
As an example, this is what I've done with my existing boards. I have 3:
cordova-ios@4.4.1 (labelled ios-next, backlog)
cordova-ios@4.5.0 (labelled backlog)
cordova-ios@5.0.0 (labelled backlog)
I will remove the first two boards (soon), knowing that I have captured
them into this new workflow.
-------------------------------
cordova-ios@4.4.1 Board:
ios-next board is for label ios-next only -- the next ios-version to be
released is 4.4.1, thus those issues are labelled with ios-next.
Once I am done with all the issues, I use the Release functionality of the
board to say that cordova-ios@4.4.1 is a release.
Currently also labelled with 'backlog', I will remove that label.
cordova-ios@4.5.0 Board:
labelled backlog so it shows in the backlog. The fix version currently is
"cordova-ios@4.5.0" to indicate planned release.
I will remove this Fix Version, and let it remain in the backlog so the
next version can be ad-hoc and the version number for released would be
according to semver.
cordova-ios@5.0.0 Board:
labelled backlog so it shows in the backlog. The fix version is
"cordova-ios@5.0.0" to indicate planned release.
This is planned because it should contain breaking changes (API change, iOS
Support change etc). When the time comes, this will be labelled 'ios-next'
since it also exists in the backlog. It still has a board for visibility
(although it can be achieved with a saved filter).
-------------------------------
From the aftermath I will have only two boards:
ios-next
cordova-ios@5.0.0 (labelled backlog, fix-version cordova-ios@5.0.0)
After an ios-next release:
1. I will triage the backlog for component: ios issues
2. Label items for the next release with "ios-next"
3. Remove the "backlog" label for these same items
As new issues come in:
1. Triage them into "backlog" label OR
2. Triage them into "ios-next" label
You move an item from the "backlog" to "ios-next (or vice-versa) by
changing the label.
Your issue should not have both labels.
=========
ISSUES:
1. Right now the 'ios-next' board is just named that, 'ios-next'. It is not
clearly visible what the next planned version is. I'm not sure how to
effectively communicate this in JIRA with the Kanban board interface. This
information should ideally be on the Board itself.
2. We should add more Admins for these boards across the PMC
On Sat, Jul 22, 2017 at 12:30 PM, Filip Maj <ma...@gmail.com> wrote:
> Hi everyone,
>
> Over the past little while, I've been trying to wrap my head around
> what open issues exist within Cordova, which ones are top priority +
> how we can identify the most pressing issues, and how to bubble those
> up to the top for PMC members and contributor/committers.
>
> With some of the other Adobians, we've slapped together a few JIRA
> boards that we think can help wrangle the 2,054+ unresolved issues in
> JIRA [1]. The idea is to use two labels to differentiate between
> issues identified as "we need to fix this for the next release" and
> "we need to fix this at some point in the future."
>
> One board is called the "Cordova Backlog" [2]. It shows open or in
> progress issues for _all_ components / repos within Cordova that are
> tagged with the 'backlog' label. I think this board helps to
> identify/aggregate triaged issues that committers/PMC members feel are
> important enough to address at some point - but not necessarily for
> the next release. It also gives a nice high-level overview of Cordova
> as a whole since it shows issues across all repos. To make an issue
> show up in this board, simply add the 'backlog' label to a JIRA issue.
>
> To complement this, and make working towards the next release for
> particular components easier, we've added a set of boards we've called
> "Next". These boards are per-component (or roughly, per group of
> related components), and show open, in progress and completed issues.
> The idea with these boards is to give specific repo maintainers +
> contributors a shared todo list as they work towards nailing a
> release. We already had a "cordova-next" board in the past which was
> mainly used in prep for major version releases of the tooling - this
> board has been renamed "tools-next." The specific boards created are:
> - browser-next [3] for the cordova-browser platform
> - docs-next [4] for cordova-docs
> - plugins-next [5] for all cordova plugins
> - android-next [6] for cordova-android
> - tools-next [7] for all cordova tooling (cli, lib, fetch, create, etc.)
> - ios-next [8] for cordova-ios
> - windows-next [9] for cordova-windows
>
> To make an issue show up in one of these, apply the relevant *-next
> label to an issue, i.e. android-next, or docs-next, or browser-next.
> The "release" link available on these boards could also be used to
> help create changelogs.
>
> So, to summarize:
> - hoping this can create visibility and a shared backlog / work list
> to help with collaboration between contributors
> - hoping a consistent approach across repos can help increase
> transparency and lower confusion as contributors work across repos
>
> Open to any comments or questions! My goal with this is to try to
> create a shared workflow for contributors, that is relatively
> consistent across components, in order to increase ease of
> collaboration - this is not set in stone, but rather a first stab, so
> I am open to all ideas to try to make this more accessible for
> everyone.
>
> Cheers,
> Fil
>
>
> [1] https://issues.apache.org/jira/secure/ConfigureReport.
> jspa?filterid=12320364&mapper=components&selectedProjectId=
> 12312420&reportKey=com.atlassian.jira.plugin.system.
> reports%3Asinglelevelgroupby&Next=Next
> [2] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=195
> [3] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=193
> [4] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=198
> [5] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=194
> [6] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=190
> [7] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=171
> [8] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=192
> [9] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=191
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>