Awesome!

On Tue, Dec 11, 2018 at 9:39 AM Mark Waite <[email protected]>
wrote:

> 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
>    <https://github.com/jenkinsci/git-client-plugin/milestone/1>
>    - Git plugin 4.0 <https://github.com/jenkinsci/git-plugin/milestone/3>
>    - Git client plugin "Later"
>    <https://github.com/jenkinsci/git-client-plugin/milestone/2?closed=1>
>    (closed for now, intending to reopen once the higher priority reviews
>    are resolved)
>    - Git plugin "Later"
>    <https://github.com/jenkinsci/git-plugin/milestone/4?closed=1> (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
>
> On Sun, Dec 9, 2018 at 7:45 PM Mark Waite <[email protected]>
> wrote:
>
>> Here are the results of my tagging:
>>
>>    1. BuildData bloat
>>    <https://github.com/jenkinsci/git-plugin/labels/1%20-%20BuildData>
>>    2. notifyCommit
>>    <https://github.com/jenkinsci/git-plugin/labels/2%20-%20notifyCommit>
>>    3. Submodules
>>    <https://github.com/jenkinsci/git-plugin/labels/3%20-%20Submodules>
>>    4. Caching
>>    <https://github.com/jenkinsci/git-plugin/labels/4%20-%20Caching>
>>    5. Changelog
>>    <https://github.com/jenkinsci/git-plugin/labels/5%20-%20Changelog>
>>
>> Thanks for the suggestion.  We'll see how it works.
>>
>> Mark Waite
>>
>> On Sun, Dec 9, 2018 at 6:56 PM Mark Waite <[email protected]>
>> wrote:
>>
>>>
>>>
>>> On Sun, Dec 9, 2018 at 2:52 PM Liam Newman <[email protected]> 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
>>>
>>>
>>>> Changing labels is tracked and visible, and I don't think
>>>> non-collaborators can change them.
>>>>
>>>>
>>>>
>>>> On Sunday, December 9, 2018 at 11:58:47 AM UTC-8, Stephen Connolly
>>>> wrote:
>>>>>
>>>>>
>>>>>
>>>>> On Sun 9 Dec 2018 at 15:35, Mark Waite <[email protected]> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Dec 9, 2018 at 8:18 AM Daniel Beck <[email protected]> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> > On 9. Dec 2018, at 15:34, Mark Waite <[email protected]> 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 [email protected].
>>>>>>> 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 [email protected].
>>>>>> To view this discussion on the web visit
>>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtH3uO4bGPaCbxJEmpJtZ8sn5BYZ5%2BXJ4Jn%3DUB1CuEUePA%40mail.gmail.com
>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtH3uO4bGPaCbxJEmpJtZ8sn5BYZ5%2BXJ4Jn%3DUB1CuEUePA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>> --
>>>>> Sent from my phone
>>>>>
>>>> --
>>>> 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 [email protected].
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/jenkinsci-dev/e90320d5-9f4d-45ad-a89c-73384f237e62%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/e90320d5-9f4d-45ad-a89c-73384f237e62%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>> --
>>> Thanks!
>>> Mark Waite
>>>
>>
>>
>> --
>> Thanks!
>> Mark Waite
>>
>
>
> --
> 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 [email protected].
> 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
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFwFU7t_Lz%2BdJC0JvkFNKuk_Kzc%2Bw_Y%3DK898LKMSQ-qTw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAA0qCNwsf0tc3%2Bf7s5ajfN-NdTDU1goEANDN4n935%3DQ6%3DyNPjw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to