mirror of
https://github.com/semver/semver.git
synced 2026-07-11 05:12:48 -05:00
[GH-ISSUE #418] We need more issue labels and contributors should have access to them. #6299
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/semver#6299
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jwdonahue on GitHub (Dec 14, 2017).
Original GitHub issue: https://github.com/semver/semver/issues/418
I have just completed a comprehensive review of all the open issues here at semver/semver. I found myself wishing I could apply tags or labels to them as I went along. It turns out that GitHub offers some support for labels in Issues and Pull-requests, but they do not seem to be accessible with my current status and/or the current repo configuration.
The current set of defined labels are:
Only a subset of the typical tags I am used to seeing on well managed projects, and completely useless to me because they are not available. Even as I write-up this issue, I am not presented with any way to categorize this issue through the use of tags/labels. @mojombo & @Haacked, please fix this. I propose the following set of labels should be added to the above list:
-- Use when you have a proposed answer for a question.
-- Use when one of the semver maintainers has reviewed an issue, with or without reply.
-- An argument has been made to close an issue and the OP has been explicitly asked to close. This is for reviewers to mark issues that maintainers should probably close. You could filter on Answer & Close requested that are older than some reasonable number of days or weeks, and focus your valuable time on closing those.
-- Some of the best proposals that I have seen posted here, should be stand-alone/foreign standards that SemVer should cross-link to. There's currently a dearth of such standards, but maybe if we encourage them, they will come?
-- Lots of good proposals would be breaking changes. Whether or not there's ever going to be an effort to begin work on SemVer 3.x.x, this would be a good label for those. Punt plus Close Requested would save the maintainers some time when pruning issues.
-- In the spec world, this is a bug report (issues) or fix (PR).
-- For spec defects in logic or other issues that don't fall into spelling or grammar.
The above would be a good start IMO.
References:
@jwdonahue commented on GitHub (Dec 27, 2017):
Awesome! Thank you.