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" <neilcsm...@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 <netbe...@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-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@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-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@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-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
