You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@trafficcontrol.apache.org by Zach Hoffman <zr...@apache.org> on 2020/09/18 00:55:27 UTC
Separate bug and feature/improvement request issue templates
Hey all,
I just submitted a PR to get us separate issue templates for bugs and
feature/improvement requests:
https://github.com/apache/trafficcontrol/pull/5047
To see what it would look like, visit
https://github.com/zrhoffman/trafficcontrol/issues/new/choose and test out
the different links:
• Bug report
• Feature request
• Improvement request
• Report a security vulnerability
• Discuss the project (links to the page about our mailing lists)
• Support questions (links to the Slack)
The immediate benefit of this is that the instructions in each issue
template apply to the type of issue a user wants to submit. Since there are
links to the mailing lists and Slack on the issue creation page, a
secondary benefit is boosting the ease of joining our community.
When someone creates an issue categorized as a bug report, it automatically
adds the _bug_ label. When someone creates an issue categorized as a new
feature or as an improvement request, it adds the _enhancement_ label. I
considered also adding the _tech debt_ label to improvement requests, but
that might lead to overuse of that label.
Let me know what you all think (or leave a comment on the PR)!
-Zach
Re: Separate bug and feature/improvement request issue templates
Posted by Zach Hoffman <zr...@apache.org>.
https://github.com/apache/trafficcontrol/pull/5047 is merged! Feel free to
open a new issue or PR on GitHub if anyone sees anything they think should
be changed.
-Zach
On Fri, Sep 18, 2020 at 12:06 PM Jeremy Mitchell <mi...@gmail.com>
wrote:
> Very slick. I like it!
>
> On Thu, Sep 17, 2020 at 7:03 PM Zach Hoffman <zr...@apache.org> wrote:
>
>> > When someone creates an issue categorized as a new feature or as an
>> improvement request, it adds the _enhancement_ label. I considered also
>> adding the _tech debt_ label to improvement requests, but that might lead
>> to overuse of that label.
>>
>> Oh, we have an _improvement_ label. That's what improvement requests get
>> labeled with now.
>>
>> -Zach
>>
>> On Thu, Sep 17, 2020 at 6:55 PM Zach Hoffman <zr...@apache.org>
>> wrote:
>>
>>> Hey all,
>>>
>>> I just submitted a PR to get us separate issue templates for bugs and
>>> feature/improvement requests:
>>> https://github.com/apache/trafficcontrol/pull/5047
>>>
>>> To see what it would look like, visit
>>> https://github.com/zrhoffman/trafficcontrol/issues/new/choose and test
>>> out the different links:
>>>
>>> • Bug report
>>> • Feature request
>>> • Improvement request
>>> • Report a security vulnerability
>>> • Discuss the project (links to the page about our mailing lists)
>>> • Support questions (links to the Slack)
>>>
>>> The immediate benefit of this is that the instructions in each issue
>>> template apply to the type of issue a user wants to submit. Since there are
>>> links to the mailing lists and Slack on the issue creation page, a
>>> secondary benefit is boosting the ease of joining our community.
>>>
>>> When someone creates an issue categorized as a bug report, it
>>> automatically adds the _bug_ label. When someone creates an issue
>>> categorized as a new feature or as an improvement request, it adds the
>>> _enhancement_ label. I considered also adding the _tech debt_ label to
>>> improvement requests, but that might lead to overuse of that label.
>>>
>>> Let me know what you all think (or leave a comment on the PR)!
>>>
>>> -Zach
>>>
>>
Re: Separate bug and feature/improvement request issue templates
Posted by Jeremy Mitchell <mi...@gmail.com>.
Very slick. I like it!
On Thu, Sep 17, 2020 at 7:03 PM Zach Hoffman <zr...@apache.org> wrote:
> > When someone creates an issue categorized as a new feature or as an
> improvement request, it adds the _enhancement_ label. I considered also
> adding the _tech debt_ label to improvement requests, but that might lead
> to overuse of that label.
>
> Oh, we have an _improvement_ label. That's what improvement requests get
> labeled with now.
>
> -Zach
>
> On Thu, Sep 17, 2020 at 6:55 PM Zach Hoffman <zr...@apache.org> wrote:
>
>> Hey all,
>>
>> I just submitted a PR to get us separate issue templates for bugs and
>> feature/improvement requests:
>> https://github.com/apache/trafficcontrol/pull/5047
>>
>> To see what it would look like, visit
>> https://github.com/zrhoffman/trafficcontrol/issues/new/choose and test
>> out the different links:
>>
>> • Bug report
>> • Feature request
>> • Improvement request
>> • Report a security vulnerability
>> • Discuss the project (links to the page about our mailing lists)
>> • Support questions (links to the Slack)
>>
>> The immediate benefit of this is that the instructions in each issue
>> template apply to the type of issue a user wants to submit. Since there are
>> links to the mailing lists and Slack on the issue creation page, a
>> secondary benefit is boosting the ease of joining our community.
>>
>> When someone creates an issue categorized as a bug report, it
>> automatically adds the _bug_ label. When someone creates an issue
>> categorized as a new feature or as an improvement request, it adds the
>> _enhancement_ label. I considered also adding the _tech debt_ label to
>> improvement requests, but that might lead to overuse of that label.
>>
>> Let me know what you all think (or leave a comment on the PR)!
>>
>> -Zach
>>
>
Re: Separate bug and feature/improvement request issue templates
Posted by Zach Hoffman <zr...@apache.org>.
> When someone creates an issue categorized as a new feature or as an
improvement request, it adds the _enhancement_ label. I considered also
adding the _tech debt_ label to improvement requests, but that might lead
to overuse of that label.
Oh, we have an _improvement_ label. That's what improvement requests get
labeled with now.
-Zach
On Thu, Sep 17, 2020 at 6:55 PM Zach Hoffman <zr...@apache.org> wrote:
> Hey all,
>
> I just submitted a PR to get us separate issue templates for bugs and
> feature/improvement requests:
> https://github.com/apache/trafficcontrol/pull/5047
>
> To see what it would look like, visit
> https://github.com/zrhoffman/trafficcontrol/issues/new/choose and test
> out the different links:
>
> • Bug report
> • Feature request
> • Improvement request
> • Report a security vulnerability
> • Discuss the project (links to the page about our mailing lists)
> • Support questions (links to the Slack)
>
> The immediate benefit of this is that the instructions in each issue
> template apply to the type of issue a user wants to submit. Since there are
> links to the mailing lists and Slack on the issue creation page, a
> secondary benefit is boosting the ease of joining our community.
>
> When someone creates an issue categorized as a bug report, it
> automatically adds the _bug_ label. When someone creates an issue
> categorized as a new feature or as an improvement request, it adds the
> _enhancement_ label. I considered also adding the _tech debt_ label to
> improvement requests, but that might lead to overuse of that label.
>
> Let me know what you all think (or leave a comment on the PR)!
>
> -Zach
>