One thing I saw proposed elsewhere is to group labels, by naming them
group:label.
Am 17.04.2015 um 07:40 schrieb James Crist:
*Submodule tags (html #0000FF, blue):*
Everything after `sympy.` for the specific submodule. Keep the naming and
casing consistent with the sympy namespace. If the relevant submodule is
small, group it in with it's parent submodule. Feel free to create new
labels if needed. Multiple tags may be used, but only if needed.
i.e. area:evalf, area:integrals, etc.
*Classifier tags (html #d4c5f9, light purple):*
What kind of issue is this. Currently 3 supported:
- `valid`: valid bug *in current master* (will be renamed to bug later, see
below)
- `wontfix`: not a bug, should be tagged and closed (once everyone
agrees/explanation given of course!)
- `duplicate`: same issue already exists. Main issue should be linked, and
the duplicate closed.
status:valid, status:wontfix, status: duplicate
- `enhancement`: not a bug, but something that would be nice to have
type:bug, type:enhancement
*Platform tags (html #800080, purple):*
Things that have to deal with specific platforms, python versions. This
includes `IPython`, `Python 3`, other versions such as `PyPy`, etc...,
`Windows`, and `SymPy Gamma`/`SymPy Live`. I feel like the last 2 should be
moved to their respective repositorys, but I don't know how to export
issues (it may not even be possible). I'd like to consolidate these if
possible, but current system isn't terrible.
platform:python.3 etc.
*Priority tags (html #eb6420, orangeish?):*
How important this is to sympy. I don't like these, as almost everything is
marked as medium. I feel they don't provide a level of information that we
actually care about, and a better triaging system could be used. Mainly,
priority is relative - what's important to some users may be irrelevant to
others. Really, only the `critical` tag has been used to some success. But,
as we were using them before, let's keep them for now.
One policy I just saw was "we see everything as normal, and have an
'urgent' classification, so we didn't see a need for 'low'".
I do not even see a reason for priority:urgent. Different things are
urgent for different people, so maybe something like
attention:release (for release blockers)
attention:security (for security holes - just an example, it's
irrelevant for SymPy)
attention:<whatever team we might else have>
*Meta tags (html #c7def8, sky blue):*
Issues that have to deal with non-code functionality. Testing and
documentation tags are obvious, `Maintainability` has to do with how we
organize code/code quality/dev environment issues.
*Special tags (html #f7c6c7, pink):*
Things that need their own issue and need to stand out. Right now this is
deprecation warning removal issues, as they're important and should be
easily visible, and `Needs decision` labels.
That might be attention:release.
Or maybe trigger:release-0.7.8 for issues that should have a review
trigger. (OTOH I don't like triggers; they tend to be done twice, and
afterwards everybody things they's be the second one. It's usually
better to have a status that people automatically know when to reset,
something labelled "trigger:" won't make them reset it.)
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sympy.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sympy/5531633F.2030802%40durchholz.org.
For more options, visit https://groups.google.com/d/optout.
