Re: Issue management issues (meta-issues?!)
On Tue, 7 Feb 2023 at 01:51, Ernie Rael wrote: > I think "NeedsTriage" has a meaning beyond that someone has made a comment. > How about "NeedsTriage" can only be taken away when either "Bug" or > "FeatureRequest" or ??? is added. "Bug" or "Feature Request" labels are added depending on which form the user fills out. They're not a useful trigger. Adding additional labels might be. Although I sometimes label issues without responding so they're visible to other committers with more knowledge in that area. I agree that need:triage implies more than a comment, but the idea was that the issue ends up in one of 3 states after a committer has commented (or at least considered) - valid, invalid or needs more information. Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Issue management issues (meta-issues?!)
On 23/02/06 12:34 PM, Neil C Smith wrote: On Sat, 4 Feb 2023 at 00:51, Michael Bien wrote: yeah it seems like nobody is using the triage label the way it was originally intended. We could probably just remove that label (or don't let gh set it by default at the very least). If something is missing labels it is probably not triaged. I'd prefer to keep a label. Possibly even more likely to accumulate unanswered issues without? One of the original intentions was to allow us to use GH actions for some automation. We could remove the label automatically if a committer replies? I think "NeedsTriage" has a meaning beyond that someone has made a comment. How about "NeedsTriage" can only be taken away when either "Bug" or "FeatureRequest" or ??? is added. -ernie Could even email a report of older issues without a response on a regular basis? and probably more. Should we prefix all issue specific labels with 'issue:'? So that they are easier to find in the search? Mentioning 'issue' in the label description would have a similar effect. Possibly would help. Need to check whether they're used, and make sure we don't rename any with special meaning though. Incidentally, also need to handle the fact that GH changed the forms so that required dropdowns are being populated - I think that's why we've had more offers of PRs! :-) Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Issue management issues (meta-issues?!)
On 06.02.23 21:34, Neil C Smith wrote: On Sat, 4 Feb 2023 at 00:51, Michael Bien wrote: yeah it seems like nobody is using the triage label the way it was originally intended. We could probably just remove that label (or don't let gh set it by default at the very least). If something is missing labels it is probably not triaged. I'd prefer to keep a label. Possibly even more likely to accumulate unanswered issues without? One of the original intentions was to allow us to use GH actions for some automation. We could remove the label automatically if a committer replies? in theory yes. In practice: - the workflow might need write permission for that, current workflows are intentionally kept without that permission (this is also the apache default last time i checked) - the workflow would have to check who is an apache committer Could even email a report of older issues without a response on a regular basis? please no :) Not to me at least. gh CLI can probably generate that list. I used it from scripts for another project before. gh issue list --label "needs:triage" --search "sort:created-asc" second entry point is via the search (has filters for comment count etc): gh search issues [] [flags] (don't run more than 5k queries per hour) and probably more. Should we prefix all issue specific labels with 'issue:'? So that they are easier to find in the search? Mentioning 'issue' in the label description would have a similar effect. Possibly would help. Need to check whether they're used, and make sure we don't rename any with special meaning though. yeah. Ideally they shouldn't show up in main.yml and release.yml... and doesn't hurt to check the rest too. Adding a label description should be always safe. Incidentally, also need to handle the fact that GH changed the forms so that required dropdowns are being populated - I think that's why we've had more offers of PRs! :-) we should interpret this as commitment and let a github action ask the user once per week where the PR is :) -mbien Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Issue management issues (meta-issues?!)
On Sat, 4 Feb 2023 at 00:51, Michael Bien wrote: > yeah it seems like nobody is using the triage label the way it was > originally intended. > > We could probably just remove that label (or don't let gh set it by > default at the very least). If something is missing labels it is > probably not triaged. I'd prefer to keep a label. Possibly even more likely to accumulate unanswered issues without? One of the original intentions was to allow us to use GH actions for some automation. We could remove the label automatically if a committer replies? Could even email a report of older issues without a response on a regular basis? > and probably more. Should we prefix all issue specific labels with > 'issue:'? So that they are easier to find in the search? Mentioning > 'issue' in the label description would have a similar effect. Possibly would help. Need to check whether they're used, and make sure we don't rename any with special meaning though. Incidentally, also need to handle the fact that GH changed the forms so that required dropdowns are being populated - I think that's why we've had more offers of PRs! :-) Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Issue management issues (meta-issues?!)
On 30.01.23 16:38, Neil C Smith wrote: Hi all, Doing my usual trawl through the issue space leading up to releases. It's not quite as bad as the JIRA was .. yet! :-) We've got about 13 pages of issues with needs:triage on them at the moment. A lot of those have responses on them already. It's possible we should have used a different label for that, but the original plan was - - if you're the first committer to add a reply, please remove the needs:triage label. - if you've asked the reporter for more info, please add the pending-response label so that we can close them if we don't get that. - if it's invalid, close it, or convert it into a discussion. - if it's got this far it should at least be an actionable issue. Even if we stick "contribution welcome" on it! :-) Oh, and feel free to stick milestones and priorities on to help us with release management. Do we change needs:triage to needs:response or similar? Might be closer to the original intention. yeah it seems like nobody is using the triage label the way it was originally intended. We could probably just remove that label (or don't let gh set it by default at the very least). If something is missing labels it is probably not triaged. we got: https://github.com/apache/netbeans/labels/pending-response https://github.com/apache/netbeans/labels/More%20info%20needed https://github.com/apache/netbeans/labels/can%20not%20reproduce https://github.com/apache/netbeans/labels/already%20fixed https://github.com/apache/netbeans/labels/duplicate https://github.com/apache/netbeans/labels/caused-by-plugin https://github.com/apache/netbeans/labels/invalid and probably more. Should we prefix all issue specific labels with 'issue:'? So that they are easier to find in the search? Mentioning 'issue' in the label description would have a similar effect. -mbien Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Issue management issues (meta-issues?!)
Hi all, Doing my usual trawl through the issue space leading up to releases. It's not quite as bad as the JIRA was .. yet! :-) We've got about 13 pages of issues with needs:triage on them at the moment. A lot of those have responses on them already. It's possible we should have used a different label for that, but the original plan was - - if you're the first committer to add a reply, please remove the needs:triage label. - if you've asked the reporter for more info, please add the pending-response label so that we can close them if we don't get that. - if it's invalid, close it, or convert it into a discussion. - if it's got this far it should at least be an actionable issue. Even if we stick "contribution welcome" on it! :-) Oh, and feel free to stick milestones and priorities on to help us with release management. Do we change needs:triage to needs:response or similar? Might be closer to the original intention. Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
