You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Neil C Smith <ne...@apache.org> on 2022/01/06 15:38:01 UTC
GitHub issues - initial templates and labels
Hi All,
Following the lazy consensus thread I've started work on porting
Airflow's issue forms for NetBeans, making changes where necessary.
There is an in progress PR at https://github.com/apache/netbeans/pull/3415
I've set up a temporary repository so these can be looked at
https://github.com/codelerity/netbeans-issues-test/issues/new Please
have a look, and feel free to open test issues if you want. Review
via the PR if necessary.
I'll contact infra@ about enabling discussions - links to that will
404 at the moment.
I need to configure labelling - this will be loosely based on
Airflow's again ( https://github.com/apache/airflow/labels )
particularly with prefixes. I won't enable automation in the above
PR, but we can as we go.
One key label that will be applied to all user submitted issues is
needs:triage. Once we enable, if you're the first committer to notice
an issue with that label, please take a look at it! Either verify
it's a reproducible issue and remove the triage label, ask the
reporter for more information and label with pending-response, move
the issue to discussions if it's incomplete, or close if it's invalid.
## Areas
In terms of other labels, I'm planning to prefix all the existing
section labels with area: eg.
area:Gradle
area:LSP
## Priorities
priority:critical
priority:high
I'm only thinking of adding those two for now. With critical reserved
for "must address in next release" issues / PRs. Rather than low
priority, maybe we can add a contribution-welcome or similar?
## Kinds of issue
kind:bug
kind:feature
kind:meta
The meta issue label is applied by the issue form reserved for
NetBeans committers. That's there for overarching task tracking now
there's no need for issues for PRs.
## Other key labels
needs:triage - requires attention from a committer - you see it, you
handle it! :-)
needs:discussion - requires discussion on this mailing list
pending-response - requires more information from the reporter
(Airflow has automation to close these off automatically after a
period of time)
Any thoughts or concerns, please speak up. I'll look to merge /
complete this first stage early next week.
Thanks,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: GitHub issues - initial templates and labels
Posted by Neil C Smith <ne...@apache.org>.
On Thu, 6 Jan 2022, 19:30 Eric Bresie, <eb...@gmail.com> wrote:
> So would “critical” be used to address “show / release stopper” level
> issues ...
>
Yes, basically replacing how we (say we) treat blocker now.
>
> Is there a “default” for this?
>
No label (for priority, other labels are added by the form)
Given the change many might always assumes it “critical”
> ;-).
>
Tough! Lots of reporters think their issue is critical or a blocker on JIRA
currently, irrespective of our criteria. Non-committers don't get to add
labels. All these labels are for committer use only.
Neil
Re: GitHub issues - initial templates and labels
Posted by Eric Bresie <eb...@gmail.com>.
So would “critical” be used to address “show / release stopper” level
issues or just the severity in general?
And semantics I’m sure but is the for “in next release” does this mean a
“coming release” or some “future release”?
Is there a “default” for this?
Should there be some sort of “New” or “None” to imply it has not been
determine yet? Given the change many might always assumes it “critical”
;-). Although suppose this would potentially result in a lot of un-defined
severities,
------------------------------
*From:* Michael Bien <mb...@gmail.com>
*Sent:* Thursday, January 6, 2022 9:53 AM
*To:* dev@netbeans.apache.org; Neil C Smith
*Subject:* Re: GitHub issues - initial templates and labels
On 06.01.22 16:38, Neil C Smith wrote:
> ## Priorities
>
> priority:critical
> priority:high
>
> I'm only thinking of adding those two for now. With critical reserved
> for "must address in next release" issues / PRs. Rather than low
> priority, maybe we can add a contribution-welcome or similar?
>
I think there should be a low priority. There are little annoyances or
"quality of life" issues which should not be set to high prio. (which
would happen if there is no other choice)
contribution-welcome: could this be a label?
-michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
--
Eric Bresie
ebresie@gmail.com
Re: GitHub issues - initial templates and labels
Posted by Michael Bien <mb...@gmail.com>.
On 06.01.22 17:09, Neil C Smith wrote:
> On Thu, 6 Jan 2022 at 15:52, Michael Bien <mb...@gmail.com> wrote:
>> On 06.01.22 16:38, Neil C Smith wrote:
>>> ## Priorities
>>>
>>> priority:critical
>>> priority:high
>>>
>>> I'm only thinking of adding those two for now. With critical reserved
>>> for "must address in next release" issues / PRs. Rather than low
>>> priority, maybe we can add a contribution-welcome or similar?
>>>
>> I think there should be a low priority. There are little annoyances or
>> "quality of life" issues which should not be set to high prio. (which
>> would happen if there is no other choice)
>>
>> contribution-welcome: could this be a label?
> Bear in mind, the default would be no priority label. We only need to
> put a priority label on an issue where there's a need to track it.
ah i see. I forgot for a moment that everything is a label now. This
makes sense of course! No need for low.
-michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: GitHub issues - initial templates and labels
Posted by Neil C Smith <ne...@apache.org>.
On Thu, 6 Jan 2022 at 15:52, Michael Bien <mb...@gmail.com> wrote:
>
> On 06.01.22 16:38, Neil C Smith wrote:
> > ## Priorities
> >
> > priority:critical
> > priority:high
> >
> > I'm only thinking of adding those two for now. With critical reserved
> > for "must address in next release" issues / PRs. Rather than low
> > priority, maybe we can add a contribution-welcome or similar?
> >
> I think there should be a low priority. There are little annoyances or
> "quality of life" issues which should not be set to high prio. (which
> would happen if there is no other choice)
>
> contribution-welcome: could this be a label?
Bear in mind, the default would be no priority label. We only need to
put a priority label on an issue where there's a need to track it.
My thinking was that there's a need to mark things that are lower than
normal priority where we are basically saying we would accept a fix,
but it's unlikely someone here is going to do it any time soon - ie.
encouraging the reporter or others who do consider it a priority to
work on it? So yes, "contribution-welcome" was suggested as a label.
It seemed a little friendlier than telling someone their issue isn't
important to us! :-)
That reminds me that Geertjan and I had a conversation a while back
about the little annoyances that are quick fixes being labelled
"papercuts" along the lines of
https://wiki.ubuntu.com/One%20Hundred%20Papercuts/Mission
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: GitHub issues - initial templates and labels
Posted by Michael Bien <mb...@gmail.com>.
On 06.01.22 16:38, Neil C Smith wrote:
> ## Priorities
>
> priority:critical
> priority:high
>
> I'm only thinking of adding those two for now. With critical reserved
> for "must address in next release" issues / PRs. Rather than low
> priority, maybe we can add a contribution-welcome or similar?
>
I think there should be a low priority. There are little annoyances or
"quality of life" issues which should not be set to high prio. (which
would happen if there is no other choice)
contribution-welcome: could this be a label?
-michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: GitHub issues - initial templates and labels
Posted by Neil C Smith <ne...@apache.org>.
On Thu, 6 Jan 2022 at 17:07, Neil C Smith <ne...@apache.org> wrote:
> > Maybe I'm missing something obvious, but IMHO the focus should be how
> > to streamline fixes from drive-by contributors. For this we need a
> > form, where people can document, that they agree to the donation
> > without having an ICLA on file.
>
> Opening a PR against the NetBeans repository is (usually) enough in
> itself! Clause #5 of the ASL.
And incidentally, we could follow Airflow's use of a pull request
template too which could make this more explicit - eg.
https://github.com/apache/airflow/blob/main/.github/PULL_REQUEST_TEMPLATE.md
I did consider adding to this PR but decided to consider separately.
And speaking of encouraging drive-by contribution, compare also -
https://github.com/apache/airflow/contribute
https://github.com/apache/netbeans/contribute
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: GitHub issues - initial templates and labels
Posted by Neil C Smith <ne...@apache.org>.
On Thu, 6 Jan 2022 at 16:41, Matthias Bläsing <mb...@doppel-helix.eu> wrote:
> Do we really want to encourage people to file issues?! My take on the
> current situation is, that there is no one really working on fixing
> issues, apart from the issues relevant to them (which is OK!).
Actually we're trying to discourage those who are not engaged enough ...
> While I like the form, I don't see an improvement relative to JIRA. As
> long as people can file issues and then go away, we will end up with
> the same mess as bugzilla and jira.
Don't consider the form in isolation to the process. JIRA as we
currently have it set up is not working, and utterly useless for
managing releases. The plan as was previously outlined in the lazy
consensus thread involves adopting as much as possible Airflow's model
- learning from how another ASF project has addressed these problems.
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191332632
Worth reading the whole section on contributor recruitment.
> Maybe I'm missing something obvious, but IMHO the focus should be how
> to streamline fixes from drive-by contributors. For this we need a
> form, where people can document, that they agree to the donation
> without having an ICLA on file.
Opening a PR against the NetBeans repository is (usually) enough in
itself! Clause #5 of the ASL.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: GitHub issues - initial templates and labels
Posted by Neil C Smith <ne...@apache.org>.
On Sun, 9 Jan 2022, 15:34 Matthias Bläsing, <mb...@doppel-helix.eu>
wrote:
> So people asking for an open tracker have to answer the question:
>
> - Who triages issues?
> - Who ensures bugfixes are tied to their issue reports?
> - Who ensures that issues are checked if they are gone in newer
> versions?
>
Every committer, as well as the community on this list, or we give up on
having an open issue tracker. It's that simple. It's not someone else's job.
A key reason for bringing it into the same system as the code review,
increase the amount of required information, allow for non reproducible
issues and user questions to be converted into discussions, not need
tickets for PRs, etc. is to try and make it more useful and less time
consuming for us all to manage.
Airflow have managed to make this work better for them. Yes it's about
being open and welcoming, but it's also about pre-filtering incomplete
information and encouraging contributions.
Best wishes,
Neil
Re: GitHub issues - initial templates and labels
Posted by Matthias Bläsing <mb...@doppel-helix.eu>.
Hi Christian,
my point is, that a welcoming issue tracker is an illusion for users.
The reality is, that most issue reports will be unanswered and ignored.
That is a reality now and was a reality when NetBeans was driven by
Oracle.
While it would nice if a shitload of people here would only wait for
issues to come in and fix, it is far from reality.
So people asking for an open tracker have to answer the question:
- Who triages issues?
- Who ensures bugfixes are tied to their issue reports?
- Who ensures that issues are checked if they are gone in newer
versions?
This is my opinion, but I won't stay in the way of people wanting to
make people feel welcome. These people just have to understand, that
they have to deal with their capacity and can't require others to
follow or add more time.
Greetings
Matthias
Am Sonntag, dem 09.01.2022 um 15:34 +0100 schrieb Christian Lenz:
> A Software without an issue Tracker? Every software has Bugs open source or closed source doesnt’t matter. A lot of open source software also works because of they have some core members working on. I’m glad that we have some who brings effort into NetBeans still people from oracle. So first if people don’t see the issue section they will complain and more or less create PRs with their questions or they will leave NetBeans. How do other projects work under Apache? How popular are they? Are there more people who work on other projects payed by a company?
>
> At the end, we should be more active by reacting on issues and also more friendly in our communication. When I see people creating issues, I see them months later and I try to figure it out and they are not answering anymore which is normal if they didn’t get attraction asap. Maybe they switched to another IDE due to the problem? If we show the user, that they are not alone with their roblems, just to say: „hey user we are seeing you and your issue, we comment on your issue but atm, we don’t have any plans or time to fix this so please try it by your own and we will help you as much as we can“. Makes more sense than saying nothing, or saying „it works on my machine“ and leave them alone. That is much more frustrating than a good explained comment.
>
>
> Cheers
>
> Chris
>
> Von: Matthias Bläsing
> Gesendet: Donnerstag, 6. Januar 2022 17:41
> An: dev@netbeans.apache.org
> Betreff: Re: GitHub issues - initial templates and labels
>
> Hi,
>
> Am Donnerstag, dem 06.01.2022 um 10:04 -0600 schrieb Glenn Holmer:
> > On 1/6/22 09:38, Neil C Smith wrote:
> > > Following the lazy consensus thread I've started work on porting
> > > Airflow's issue forms for NetBeans, making changes where necessary.
> > >
> > > There is an in progress PR at https://github.com/apache/netbeans/pull/3415
> >
> > The bug report form is excellent. It looks welcoming, like we really
> > want people to file issues. The last thing you want is for someone to
> > start filing an issue, then give up in exasperation because it's more
> > complicated than their tax returns. I was particularly impressed by "we
> > are happy to guide you in the contribution process".
>
> Do we really want to encourage people to file issues?! My take on the
> current situation is, that there is no one really working on fixing
> issues, apart from the issues relevant to them (which is OK!).
>
> While I like the form, I don't see an improvement relative to JIRA. As
> long as people can file issues and then go away, we will end up with
> the same mess as bugzilla and jira.
>
> Maybe I'm missing something obvious, but IMHO the focus should be how
> to streamline fixes from drive-by contributors. For this we need a
> form, where people can document, that they agree to the donation
> without having an ICLA on file. That way we can source more people
> working on the code base and not lose time with useless discussion
> about legal mergability.
>
> Greetings
>
> Matthias
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
AW: GitHub issues - initial templates and labels
Posted by Christian Lenz <ch...@gmx.net>.
A Software without an issue Tracker? Every software has Bugs open source or closed source doesnt’t matter. A lot of open source software also works because of they have some core members working on. I’m glad that we have some who brings effort into NetBeans still people from oracle. So first if people don’t see the issue section they will complain and more or less create PRs with their questions or they will leave NetBeans. How do other projects work under Apache? How popular are they? Are there more people who work on other projects payed by a company?
At the end, we should be more active by reacting on issues and also more friendly in our communication. When I see people creating issues, I see them months later and I try to figure it out and they are not answering anymore which is normal if they didn’t get attraction asap. Maybe they switched to another IDE due to the problem? If we show the user, that they are not alone with their roblems, just to say: „hey user we are seeing you and your issue, we comment on your issue but atm, we don’t have any plans or time to fix this so please try it by your own and we will help you as much as we can“. Makes more sense than saying nothing, or saying „it works on my machine“ and leave them alone. That is much more frustrating than a good explained comment.
Cheers
Chris
Von: Matthias Bläsing
Gesendet: Donnerstag, 6. Januar 2022 17:41
An: dev@netbeans.apache.org
Betreff: Re: GitHub issues - initial templates and labels
Hi,
Am Donnerstag, dem 06.01.2022 um 10:04 -0600 schrieb Glenn Holmer:
> On 1/6/22 09:38, Neil C Smith wrote:
> > Following the lazy consensus thread I've started work on porting
> > Airflow's issue forms for NetBeans, making changes where necessary.
> >
> > There is an in progress PR at https://github.com/apache/netbeans/pull/3415
>
> The bug report form is excellent. It looks welcoming, like we really
> want people to file issues. The last thing you want is for someone to
> start filing an issue, then give up in exasperation because it's more
> complicated than their tax returns. I was particularly impressed by "we
> are happy to guide you in the contribution process".
Do we really want to encourage people to file issues?! My take on the
current situation is, that there is no one really working on fixing
issues, apart from the issues relevant to them (which is OK!).
While I like the form, I don't see an improvement relative to JIRA. As
long as people can file issues and then go away, we will end up with
the same mess as bugzilla and jira.
Maybe I'm missing something obvious, but IMHO the focus should be how
to streamline fixes from drive-by contributors. For this we need a
form, where people can document, that they agree to the donation
without having an ICLA on file. That way we can source more people
working on the code base and not lose time with useless discussion
about legal mergability.
Greetings
Matthias
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: GitHub issues - initial templates and labels
Posted by Neil C Smith <ne...@apache.org>.
On Thu, 6 Jan 2022 at 16:41, Matthias Bläsing <mb...@doppel-helix.eu> wrote:
> Maybe I'm missing something obvious, but IMHO the focus should be how
> to streamline fixes from drive-by contributors. For this we need a
> form, where people can document, that they agree to the donation
> without having an ICLA on file. That way we can source more people
> working on the code base and not lose time with useless discussion
> about legal mergability.
As discussed elsewhere, I don't see a particular need for this, in the
sense that it's already covered by section 5 of the Apache License
(below). I don't see any way someone can submit a PR without already
being covered by that?!
However, from an information perspective, it might be nice to be more
upfront on certain things for drive-by contributors?
We could do a PR template along the lines of
https://github.com/apache/netbeans/pull/3431
From ASL
"""
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
"""
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: GitHub issues - initial templates and labels
Posted by Matthias Bläsing <mb...@doppel-helix.eu>.
Hi,
Am Donnerstag, dem 06.01.2022 um 10:04 -0600 schrieb Glenn Holmer:
> On 1/6/22 09:38, Neil C Smith wrote:
> > Following the lazy consensus thread I've started work on porting
> > Airflow's issue forms for NetBeans, making changes where necessary.
> >
> > There is an in progress PR at https://github.com/apache/netbeans/pull/3415
>
> The bug report form is excellent. It looks welcoming, like we really
> want people to file issues. The last thing you want is for someone to
> start filing an issue, then give up in exasperation because it's more
> complicated than their tax returns. I was particularly impressed by "we
> are happy to guide you in the contribution process".
Do we really want to encourage people to file issues?! My take on the
current situation is, that there is no one really working on fixing
issues, apart from the issues relevant to them (which is OK!).
While I like the form, I don't see an improvement relative to JIRA. As
long as people can file issues and then go away, we will end up with
the same mess as bugzilla and jira.
Maybe I'm missing something obvious, but IMHO the focus should be how
to streamline fixes from drive-by contributors. For this we need a
form, where people can document, that they agree to the donation
without having an ICLA on file. That way we can source more people
working on the code base and not lose time with useless discussion
about legal mergability.
Greetings
Matthias
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: GitHub issues - initial templates and labels
Posted by Neil C Smith <ne...@apache.org>.
On Thu, 6 Jan 2022 at 16:05, Glenn Holmer <ce...@kolabnow.com.invalid> wrote:
>
> On 1/6/22 09:38, Neil C Smith wrote:
> > Following the lazy consensus thread I've started work on porting
> > Airflow's issue forms for NetBeans, making changes where necessary.
> >
> > There is an in progress PR at https://github.com/apache/netbeans/pull/3415
>
> The bug report form is excellent. It looks welcoming, like we really
> want people to file issues. The last thing you want is for someone to
> start filing an issue, then give up in exasperation because it's more
> complicated than their tax returns. I was particularly impressed by "we
> are happy to guide you in the contribution process".
Yes, I think Airflow really nailed it! I've tried to keep as much as
possible of their wording and structure while changing where needed.
I also think they balance the complexity well - not a tax return, but
also not easy to make a drive-by log dump with no context!
If you want to, compare with
https://github.com/apache/airflow/issues/new?assignees=&labels=kind%3Abug%2Carea%3Acore&template=airflow_bug_report.yml
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: GitHub issues - initial templates and labels
Posted by Glenn Holmer <ce...@kolabnow.com.INVALID>.
On 1/6/22 09:38, Neil C Smith wrote:
> Following the lazy consensus thread I've started work on porting
> Airflow's issue forms for NetBeans, making changes where necessary.
>
> There is an in progress PR at https://github.com/apache/netbeans/pull/3415
The bug report form is excellent. It looks welcoming, like we really
want people to file issues. The last thing you want is for someone to
start filing an issue, then give up in exasperation because it's more
complicated than their tax returns. I was particularly impressed by "we
are happy to guide you in the contribution process".
--
Glenn Holmer (Linux registered user #16682)
"After the vintage season came the aftermath -- and Cenbe."
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Aw: Re: GitHub issues - initial templates and labels
Posted by Neil C Smith <ne...@apache.org>.
On Fri, 14 Jan 2022, 20:42 Eric Bresie, <eb...@gmail.com> wrote:
> (2) it is different for a "Feature",
>
Yes, the forms are quite different.
Neil
Re: Aw: Re: GitHub issues - initial templates and labels
Posted by Eric Bresie <eb...@gmail.com>.
I added a few comments to the initial test issue [1]. Not sure if this is
of help.
Not sure if I missed it or if something was done by others, but I created a
test ticket for a Feature [2]. I didn't see any of the suggested
"fields" (i.e. areas, priorities, etc.) on the create page; how do the
labels and other attributes get set?
Is this
(1) by design (i.e. these may not be included on initial creation but will
be added following triage by people with specific permissions),
(2) it is different for a "Feature", or
(3) something else is going on
In the template, would it be worth adding a link to a confluence page for
"help documentation" on how this is expected to be used?
Eric Bresie
ebresie@gmail.com
[1] https://github.com/codelerity/netbeans-issues-test/issues/1
[2] https://github.com/codelerity/netbeans-issues-test/issues/4
On Fri, Jan 14, 2022 at 11:09 AM Michael Bien <mb...@gmail.com> wrote:
> tbh I think we should probably make this a text field. Everyone looking
> at the report will have to second guess what "latest" means in context
> of the date. (I do know that it is mentioned in the guiding text that
> the reporter should mention the version somewhere - not sure if this is
> enough)
>
> alternatively we could periodically update the items on the combo box as
> you mentioned before - this might be interesting if we ever wanted to
> automatically label issues with a version label.
>
> I rarely see text fields for versions on issues, but i think it could be
> useful. e.g (12.3-12.6 and latest master)
>
> -mbien
>
> On 14.01.22 16:40, Christian Lenz wrote:
> > Hey Matthias,
> >
> > sure I got your point. I just gave my opinion and see also problems when
> we will not have this.
> > I think it will be just fine to talk to the people and let them know
> enough that they shouldn't expect anything at all.
> >
> >
> > Cheers
> >
> > Chris
> >
> >> Gesendet: Freitag, 14. Januar 2022 um 12:19 Uhr
> >> Von: "Neil C Smith" <ne...@apache.org>
> >> An: dev@netbeans.apache.org
> >> Betreff: Re: GitHub issues - initial templates and labels
> >>
> >> On Wed, 12 Jan 2022 at 21:09, Benjamin Asbach <ne...@impl.it> wrote:
> >>> I'm a little bit curious how this "latest Release" field is supposed to
> >>> work? Is this moved automatically when a new release was pumped out?
> >> No, nothing is moved automatically. Bear in mind that the forms here
> >> only structure the text that the poster submits, ensuring they have to
> >> fill in some information, and giving them guidance as they do. It's
> >> still text at the end of the day, which has its pros and cons.
> >>
> >> All metadata (milestone, labels, etc.) is committer only access.
> >> Although we can do various things with parsing text to labels, etc.
> >> automatically if we really find we need to.
> >>
> >> Now, on the version specifically, I didn't copy Airflow's form exactly
> >> because that involves adding each version manually. We also need to
> >> know whether it's a bug in a release candidate or daily build. And I
> >> wanted to put something top of the form that's clear that if it's not
> >> a bug in the latest release or later build, it's the person posting
> >> the bug's job to check.
> >>
> >> I'm not sure what's there is correct - we can easily change it for
> >> future issues if it proves problematic.
> >>
> >> Also I noticed in the bug you opened and closed that you selected
> >> Third-party package. I'm curious what that is, and whether that field
> >> selection makes sense / needs work too?
> >>
> >> Best wishes,
> >>
> >> Neil
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> >> For additional commands, e-mail: dev-help@netbeans.apache.org
> >>
> >> For further information about the NetBeans mailing lists, visit:
> >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>
> >>
> >>
> >>
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > For additional commands, e-mail: dev-help@netbeans.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: Aw: Re: GitHub issues - initial templates and labels
Posted by Michael Bien <mb...@gmail.com>.
tbh I think we should probably make this a text field. Everyone looking
at the report will have to second guess what "latest" means in context
of the date. (I do know that it is mentioned in the guiding text that
the reporter should mention the version somewhere - not sure if this is
enough)
alternatively we could periodically update the items on the combo box as
you mentioned before - this might be interesting if we ever wanted to
automatically label issues with a version label.
I rarely see text fields for versions on issues, but i think it could be
useful. e.g (12.3-12.6 and latest master)
-mbien
On 14.01.22 16:40, Christian Lenz wrote:
> Hey Matthias,
>
> sure I got your point. I just gave my opinion and see also problems when we will not have this.
> I think it will be just fine to talk to the people and let them know enough that they shouldn't expect anything at all.
>
>
> Cheers
>
> Chris
>
>> Gesendet: Freitag, 14. Januar 2022 um 12:19 Uhr
>> Von: "Neil C Smith" <ne...@apache.org>
>> An: dev@netbeans.apache.org
>> Betreff: Re: GitHub issues - initial templates and labels
>>
>> On Wed, 12 Jan 2022 at 21:09, Benjamin Asbach <ne...@impl.it> wrote:
>>> I'm a little bit curious how this "latest Release" field is supposed to
>>> work? Is this moved automatically when a new release was pumped out?
>> No, nothing is moved automatically. Bear in mind that the forms here
>> only structure the text that the poster submits, ensuring they have to
>> fill in some information, and giving them guidance as they do. It's
>> still text at the end of the day, which has its pros and cons.
>>
>> All metadata (milestone, labels, etc.) is committer only access.
>> Although we can do various things with parsing text to labels, etc.
>> automatically if we really find we need to.
>>
>> Now, on the version specifically, I didn't copy Airflow's form exactly
>> because that involves adding each version manually. We also need to
>> know whether it's a bug in a release candidate or daily build. And I
>> wanted to put something top of the form that's clear that if it's not
>> a bug in the latest release or later build, it's the person posting
>> the bug's job to check.
>>
>> I'm not sure what's there is correct - we can easily change it for
>> future issues if it proves problematic.
>>
>> Also I noticed in the bug you opened and closed that you selected
>> Third-party package. I'm curious what that is, and whether that field
>> selection makes sense / needs work too?
>>
>> Best wishes,
>>
>> Neil
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
>> For additional commands, e-mail: dev-help@netbeans.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Aw: Re: GitHub issues - initial templates and labels
Posted by Christian Lenz <Ch...@gmx.net>.
Hey Matthias,
sure I got your point. I just gave my opinion and see also problems when we will not have this.
I think it will be just fine to talk to the people and let them know enough that they shouldn't expect anything at all.
Cheers
Chris
> Gesendet: Freitag, 14. Januar 2022 um 12:19 Uhr
> Von: "Neil C Smith" <ne...@apache.org>
> An: dev@netbeans.apache.org
> Betreff: Re: GitHub issues - initial templates and labels
>
> On Wed, 12 Jan 2022 at 21:09, Benjamin Asbach <ne...@impl.it> wrote:
> > I'm a little bit curious how this "latest Release" field is supposed to
> > work? Is this moved automatically when a new release was pumped out?
>
> No, nothing is moved automatically. Bear in mind that the forms here
> only structure the text that the poster submits, ensuring they have to
> fill in some information, and giving them guidance as they do. It's
> still text at the end of the day, which has its pros and cons.
>
> All metadata (milestone, labels, etc.) is committer only access.
> Although we can do various things with parsing text to labels, etc.
> automatically if we really find we need to.
>
> Now, on the version specifically, I didn't copy Airflow's form exactly
> because that involves adding each version manually. We also need to
> know whether it's a bug in a release candidate or daily build. And I
> wanted to put something top of the form that's clear that if it's not
> a bug in the latest release or later build, it's the person posting
> the bug's job to check.
>
> I'm not sure what's there is correct - we can easily change it for
> future issues if it proves problematic.
>
> Also I noticed in the bug you opened and closed that you selected
> Third-party package. I'm curious what that is, and whether that field
> selection makes sense / needs work too?
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: GitHub issues - initial templates and labels
Posted by Neil C Smith <ne...@apache.org>.
On Wed, 12 Jan 2022 at 21:09, Benjamin Asbach <ne...@impl.it> wrote:
> I'm a little bit curious how this "latest Release" field is supposed to
> work? Is this moved automatically when a new release was pumped out?
No, nothing is moved automatically. Bear in mind that the forms here
only structure the text that the poster submits, ensuring they have to
fill in some information, and giving them guidance as they do. It's
still text at the end of the day, which has its pros and cons.
All metadata (milestone, labels, etc.) is committer only access.
Although we can do various things with parsing text to labels, etc.
automatically if we really find we need to.
Now, on the version specifically, I didn't copy Airflow's form exactly
because that involves adding each version manually. We also need to
know whether it's a bug in a release candidate or daily build. And I
wanted to put something top of the form that's clear that if it's not
a bug in the latest release or later build, it's the person posting
the bug's job to check.
I'm not sure what's there is correct - we can easily change it for
future issues if it proves problematic.
Also I noticed in the bug you opened and closed that you selected
Third-party package. I'm curious what that is, and whether that field
selection makes sense / needs work too?
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: GitHub issues - initial templates and labels
Posted by Benjamin Asbach <ne...@impl.it>.
I'm a little bit curious how this "latest Release" field is supposed to
work? Is this moved automatically when a new release was pumped out?
On 2022-01-12 13:04, Neil C Smith wrote:
> On Mon, 10 Jan 2022 at 14:28, Neil C Smith <ne...@apache.org>
> wrote:
>> Just a note that, if you haven't noticed already, GitHub Discussions
>> is now enabled.
> ...
>> As this required manual setup, I had this done in advance of merging
>> the issues enabling PR to check linking is working correctly.
>
> The rest of the initial setup is now merged and issues are active.
> I've added a brief pinned issue explaining the transition.
>
> If anyone wants to cherry pick anything that's critical for NB13 from
> JIRA, feel free to do so, and in the process help work out any kinks
> in the process.
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: GitHub issues - initial templates and labels
Posted by Neil C Smith <ne...@apache.org>.
On Mon, 10 Jan 2022 at 14:28, Neil C Smith <ne...@apache.org> wrote:
> Just a note that, if you haven't noticed already, GitHub Discussions
> is now enabled.
...
> As this required manual setup, I had this done in advance of merging
> the issues enabling PR to check linking is working correctly.
The rest of the initial setup is now merged and issues are active.
I've added a brief pinned issue explaining the transition.
If anyone wants to cherry pick anything that's critical for NB13 from
JIRA, feel free to do so, and in the process help work out any kinks
in the process.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: GitHub issues - initial templates and labels
Posted by Neil C Smith <ne...@apache.org>.
On Thu, 6 Jan 2022 at 15:38, Neil C Smith <ne...@apache.org> wrote:
> I'll contact infra@ about enabling discussions - links to that will
> 404 at the moment.
Just a note that, if you haven't noticed already, GitHub Discussions
is now enabled. It seems to have been a surprise to some, even though
it was explicitly part of this plan from the beginning! :-)
As this required manual setup, I had this done in advance of merging
the issues enabling PR to check linking is working correctly.
This is obviously for user facing discussion - anything for this
(dev@) list should stay on this list. There is overlap with users@ so
as was previously brought up, we should review how that goes /
relative usage in time. I also have a pending question with infra
about configuration of archiving for discussions. Issues and
discussion archiving might warrant a separate (and probably little
subscribed!) email list to other things?
> I've set up a temporary repository so these can be looked at
> https://github.com/codelerity/netbeans-issues-test/issues/new
Just realised that should have been
https://github.com/codelerity/netbeans-issues-test/issues/new/choose
I assume the link took people without admin rights to the right place though?!
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists