Add a "refactoring" type to the issue tracker?
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 | ncoghlan@gmail.com | Brisbane, Australia
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, <ncoghlan@gmail.com> 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 | ncoghlan@gmail.com | Brisbane, Australia _______________________________________________ core-workflow mailing list -- core-workflow@python.org To unsubscribe send an email to core-workflow-leave@python.org 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 -- core-workflow@python.org To unsubscribe send an email to core-workflow-leave@python.org 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
On 14 February 2018 at 16:11, Brett Cannon <brett@python.org> wrote:
I would consider a "code health" a more general type for things that are not user-facing.
I agree "refactoring" would be too narrow, but "code health" has some of the same problems (since not all changes along these lines are going to be about code as such - e.g. syncing up changes to the docs build system). "maintainability", perhaps? Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
I'd vote for "code health". It sends a much more positive vibe than "maintainability", and covers more than "refactoring". On Wed, Feb 14, 2018 at 9:29 AM, Nick Coghlan <ncoghlan@gmail.com> wrote:
On 14 February 2018 at 16:11, Brett Cannon <brett@python.org> wrote:
I would consider a "code health" a more general type for things that are not user-facing.
I agree "refactoring" would be too narrow, but "code health" has some of the same problems (since not all changes along these lines are going to be about code as such - e.g. syncing up changes to the docs build system).
"maintainability", perhaps?
Cheers, Nick.
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia _______________________________________________ core-workflow mailing list -- core-workflow@python.org To unsubscribe send an email to core-workflow-leave@python.org 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 -- core-workflow@python.org To unsubscribe send an email to core-workflow-leave@python.org 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
-- --Guido van Rossum (python.org/~guido)
On Thu, 15 Feb 2018 14:38:39 -0500 Barry Warsaw <barry@python.org> wrote:
Brett Cannon wrote:
I would consider a "code health" a more general type for things that are not user-facing.
I've generally seen these types of issued labeled "tech debt".
Do you open a ticket when you to increase or decrease the debt? Regards Antoine.
Antoine Pitrou wrote:
On Thu, 15 Feb 2018 14:38:39 -0500 Barry Warsaw <barry@python.org> wrote:
Brett Cannon wrote:
I would consider a "code health" a more general type for things that are not user-facing.
I've generally seen these types of issued labeled "tech debt".
Do you open a ticket when you to increase or decrease the debt?
Usually I open a ticket when I recognize some tech debt that needs to be paid down. So I guess "neither" :). The tech debt is more often already there but unnoticed, than specifically when I add it knowingly, althought that is also possible and I do usually open a ticket at that time. -Barry
participants (5)
-
Antoine Pitrou -
Barry Warsaw -
Brett Cannon -
Guido van Rossum -
Nick Coghlan