On 05/04/2019 07.20, Jesse Glick wrote:
On Thu, Apr 4, 2019 at 3:26 PM Daniel Beck <[email protected]> wrote:
- New status name ("Stalled" probably)
STALLED
- one sentence description
Some work was done on this issue, but there is no clear plan for it to
be completed.
- category
IN PROGRESS
- where it sorts into the list of existing statuses
Perhaps between REOPENED and IN REVIEW.
Additionally, a complete list of transitions to add, which each consist of:
- from status
- to status
- button label (For example "Stop Progress" is the label for In Progress ->
Open)
I guess these should suffice:
IN PROGRESS → STALLED “Stalled”
IN REVIEW → STALLED “Stalled”
STALLED → IN PROGRESS “Back in progress”
STALLED → OPEN “No longer in progress”
- optionally a screen to show, and what fields it should contain
Do not think anything like that would be needed.
I am wondering, do we really want to invest so much energy to clearly
label clutter (stalled PRs) in both github and JIRA? The way I look at
it is the PR failed to deliver the fix for the issue in question but
there might be others created in the future - I is not clear to me what
value is there in forwarding this info to JIRA.
Not that I have any numbers at hand on how often such stalled PRs dies,
revives, or keep being stalled - I presume they just sit there until
closed more of then then not, but I am wondering if an efficient way to
close such PRs would not be a better time investment. We would get rid
of what I see as clutter rather then precisely label it for someone else
to do something about it later.
--
oliver
--
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/c2d4a678-fe87-c93b-5029-e16c6e2c7d07%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
