On Fri, Apr 5, 2019 at 7:43 AM Daniel Beck wrote:
> None of these would apply in all cases.
True, but I think the commonality would be that someone who is
committed to pushing it forward would not be starting from scratch.
The lack of interested reviewers is often due to the original PR being
> On 5. Apr 2019, at 08:20, Oliver Gondža wrote:
>
> 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
>
On 05/04/2019 07.20, Jesse Glick wrote:
On Thu, Apr 4, 2019 at 3:26 PM Daniel Beck 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
On Thu, Apr 4, 2019 at 3:26 PM Daniel Beck 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
> On 4. Apr 2019, at 19:24, Jesse Glick wrote:
>
> We have recently started using a `stalled-pr` label in JIRA to mark
> issues which have an associated pull request that has not been merged
> and has no immediate prospects of merging—unresolved conflicts,
> unaddressed review comments, etc.
+1 from me.
On Thu, Apr 4, 2019 at 11:24 AM Jesse Glick wrote:
> We have recently started using a `stalled-pr` label in JIRA to mark
> issues which have an associated pull request that has not been merged
> and has no immediate prospects of merging—unresolved conflicts,
> unaddressed review
We have recently started using a `stalled-pr` label in JIRA to mark
issues which have an associated pull request that has not been merged
and has no immediate prospects of merging—unresolved conflicts,
unaddressed review comments, etc. Perhaps this should be made into a
proper *Status* in JIRA so
