[core-workflow] Re: Add a "refactoring" type to the issue tracker?

Antoine Pitrou wrote: On Thu, 15 Feb 2018 14:38:39 -0500 Barry Warsaw 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

[core-workflow] Re: Add a "refactoring" type to the issue tracker?

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". -Barry ___ core-workflow mailing list -- core-workflow@python.org To

[core-workflow] Re: Add a "refactoring" type to the issue tracker?

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 wrote: > On 14 February 2018 at 16:11, Brett Cannon wrote: > > I would consider a "code

[core-workflow] Re: Add a "refactoring" type to the issue tracker?

On 14 February 2018 at 16:11, Brett Cannon 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

[core-workflow] Re: Add a "refactoring" type to the issue tracker?

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, 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