This is good opportunity for volunteers who want to participate but are
afraid of Java/NetBeans internals.
JIRA contains a lot of bug reports and some of them are incomplete,
reported for older versions or have assigned wrong component. Some of
the are kind of fire-and-forget without any reaction to additional
questions.
Any NetBeans user can check if it is clear from description what the
issue or feature request is about. Bugs for older version need to be
verified if they can be reproduced.
Here is my suggestion for website:
https://github.com/apache/netbeans-website/pull/514
Tom
On 05. 02. 21 16:00, Neil C Smith wrote:
On Fri, 5 Feb 2021 at 14:52, Eric Bresie <[email protected]> wrote:
Who is responsible for the ticket? Once included in a release should these
tickets be closed by the user, by the release manager, by some JIRA admin
with "close permissions", some member of a "CCB/Admin" group with
applicable permissions?
By anyone in this community with permissions to do so! :-)
When RM'ing I try to keep an eye on and close things I know have been
merged. But it should definitely not be solely the RM's job ...
please. We need to get a handle on how we use JIRA, because IMO it's
getting more and more unwieldy and out of sync with actual
development. It would be good to look at automating closing issues
with tagged PRs merging too.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
