Using Jenkins JIRA to record development priorities for a plugin?

[Mark Waite]

I've reviewed and prioritized how I intend to approach the many open pull requests on the git plugin.  I intend to do the same thing with the git client plugin.

I would like to record that prioritization somewhere as a way to remember things myself and in case it helps others understand the work being done and the places where they could help with code review and testing.

Is it allowed to use issues.jenkins-ci.org for that type of tracking?

If not, is it OK if I use the wiki to record that prioritization?

If not, I can certainly place that sort of prioritization in the source code repository itself.

--

Thanks!

Mark Waite

[Daniel Beck]

> On 9. Dec 2018, at 15:34, Mark Waite <mark.ea...@gmail.com> wrote:
>
> Is it allowed to use issues.jenkins-ci.org for that type of tracking?
>

I don't see why it would not be, or do you need access to features, or plugins installed, that you currently don't have?

FWIW any user can reorder issues on boards ("rank"), or change their priority, so neither is probably a good choice.

[Mark Waite]

On Sun, Dec 9, 2018 at 8:18 AM Daniel Beck <m...@beckweb.net> wrote:

> On 9. Dec 2018, at 15:34, Mark Waite <mark.ea...@gmail.com> wrote:
>
> Is it allowed to use issues.jenkins-ci.org for that type of tracking?
>

I don't see why it would not be, or do you need access to features, or plugins installed, that you currently don't have?

I am not aware of needing anything more than is already available to me.  However, I haven't tried the experiment yet, so I'm not 100% certain.

 

FWIW any user can reorder issues on boards ("rank"), or change their priority, so neither is probably a good choice.

I think that might actually be a positive rather than a negative.  If someone is willing to find the board and use it to adjust priority settings, I'd like to see their results.  If it were abused, I could always keep a local snapshot of the priorities, or place a snapshot in some other location.

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5A128BE7-EF96-40DC-9E2D-2A459B0494DD%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

--

Thanks!

Mark Waite

[Stephen Connolly]

On Sun 9 Dec 2018 at 15:35, Mark Waite <mark.ea...@gmail.com> wrote:

On Sun, Dec 9, 2018 at 8:18 AM Daniel Beck <m...@beckweb.net> wrote:

> On 9. Dec 2018, at 15:34, Mark Waite <mark.ea...@gmail.com> wrote:
>
> Is it allowed to use issues.jenkins-ci.org for that type of tracking?
>

I don't see why it would not be, or do you need access to features, or plugins installed, that you currently don't have?

I am not aware of needing anything more than is already available to me.  However, I haven't tried the experiment yet, so I'm not 100% certain.

 

FWIW any user can reorder issues on boards ("rank"), or change their priority, so neither is probably a good choice.

I think that might actually be a positive rather than a negative.  If someone is willing to find the board and use it to adjust priority settings, I'd like to see their results.  If it were abused, I could always keep a local snapshot of the priorities, or place a snapshot in some other location.

Rank is *global* so if someone has another board and your issues show on that board too, any rank adjustments will ripple AIUI

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5A128BE7-EF96-40DC-9E2D-2A459B0494DD%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

--

Thanks!

Mark Waite

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtH3uO4bGPaCbxJEmpJtZ8sn5BYZ5%2BXJ4Jn%3DUB1CuEUePA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Sent from my phone

[Liam Newman]

Mark,

What about using labels in Github?  Since these are PRs you can add whatever labels you want to them.  

Changing labels is tracked and visible, and I don't think non-collaborators can change them. 

[Mark Waite]

On Sun, Dec 9, 2018 at 2:52 PM Liam Newman <bitwi...@gmail.com> wrote:

Mark,

What about using labels in Github?  Since these are PRs you can add whatever labels you want to them.  

Labels are an interesting idea, since the highest ranked items in my prioritization could be grouped into relatively few categories.  I may try that as an easy experiment rather than wrestling with JIRA.  The categories I'd use for now would be:

• 1 - BuildData bloat
• 2 - notifyCommit (slashes in branch names, etc.)
• 3 - Submodules
• 4 - Caching and performance
• 5 - Changelog

The digit at the start of the label indicates the priority, the word in the label indicates the topic.  Those 5 topics cover over 30% of the 60+ open pull requests.  There is more work in those 5 labels than I will be able to complete in several years, so it is more than enough prioritization for my needs.

Thanks for the suggestions.

Mark Waite

 

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e90320d5-9f4d-45ad-a89c-73384f237e62%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Thanks!

Mark Waite

[Mark Waite]

Here are the results of my tagging:

1. BuildData bloat
2. notifyCommit
3. Submodules
4. Caching
5. Changelog

Thanks for the suggestion.  We'll see how it works.

Mark Waite

--

Thanks!

Mark Waite

[Mark Waite]

I've taken one step further with the git plugin and the git client plugin.  I've created GitHub milestones

• Git client plugin 3.0
• Git plugin 4.0
• Git client plugin "Later"  (closed for now, intending to reopen once the higher priority reviews are resolved)
• Git plugin "Later" (closed for now, intending to reopen once the higher priority reviews are resolved)

The "Later" milestone includes pull requests that are closed for now.  That reduces the load on the CI server continuously evaluating each pull request one each update to the master branch and records those pull requests which should be opened and evaluated after higher priority items are resolved.

Mark Waite

--

Thanks!

Mark Waite

[Liam Newman]

Awesome!

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFwFU7t_Lz%2BdJC0JvkFNKuk_Kzc%2Bw_Y%3DK898LKMSQ-qTw%40mail.gmail.com.