I would consider a "code health" a more general type for things that are not user-facing.
On Wed, Feb 14, 2018, 10:11 Nick Coghlan, <[email protected]> wrote: > For https://bugs.python.org/issue32836, I ended up picking "behaviour" > as the issue type (since we're reporting that we're using a symbol > that we don't actually use), but it did prompt the thought: should we > add a "refactoring" type to the issue tracker? > > Right now, we tend to mark refactoring changes as "enhancement", but > I'm thinking there would be value in making it clear that we don't > expect end users to notice a particular change, it's just for the > benefit of current and future maintainers. > > Cheers, > Nick. > > -- > Nick Coghlan | [email protected] | Brisbane, Australia > _______________________________________________ > core-workflow mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/ > This list is governed by the PSF Code of Conduct: > https://www.python.org/psf/codeofconduct > _______________________________________________ > core-workflow mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/ > This list is governed by the PSF Code of Conduct: > https://www.python.org/psf/codeofconduct >
_______________________________________________ core-workflow mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/ This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
_______________________________________________ core-workflow mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/ This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
