On 8/16/19 5:52 PM, Peter Kovacs wrote:
People will also if you have 10 000 open issues that are open because no one
solved them.
If people write a good bug report then fine. If nobody can work with it, they should reopen it when they are willed to
write more.
I think a LOT of this comes down to the exact handling of these tickets,
the wording in the closing comment. It should be in a welcoming tone,
politely explaining why it's being closed, encouraging people to help us
help them by providing more insight into their issues.
My 2 cent
Am 16. August 2019 15:31:33 MESZ schrieb Scott Palmer <swpal...@gmail.com>:
Please NEVER close an issue that has not been verified as fixed or
no-longer relevant.
That is the #1 way to discourage participation. "I report the bug -
nobody fixed it , they just closed the issue without even considering
it" … that’s a crap way to do things.
By all means change the state of the issue to indicate more information
is needed. Like, “This was reported against 8.2, does this still occur
in 11.1?” (Why wouldn’t it still be a problem if it hasn’t been marked
fixed already?)
If the module hasn’t been donated yet, but it will be, why would you
intentionally lose all that feedback about what still needs to be
fixed?
Deferring an issue is not the same as closing an issue. If you haven’t
verified the issue is fixed DO NOT CLOSE it. Thats just giving the
finger to the community that bothered to report the issue and try to
help make NetBeans better.
A better approach would be to script something that went through old
opened issues and asked for them to be re-evaluated by the submitter
(if they are still around).
Scott
On Aug 13, 2019, at 4:23 pm, Matthias Bläsing
<mblaes...@doppel-helix.eu> wrote:
Hi,
Am Montag, den 12.08.2019, 16:10 +0200 schrieb Geertjan Wielenga:
There's understandable frustration by people reporting issues ( such
as our
issue filer hero Chris Lenz :-) ) about issues being filed and not
being
responded to.
this might sound rude, but at this time I would no encourage people
to
file new issues. We need people working on reviewing PRs and fixing
things.
People wanting to help, but not code, could triage the issues:
* close bugs reported against 8.2 with the request to verify against
11.1
* bugs referencing not yet donated/removed modules (hibernate, CND)
should be closed, as they are currently noise which distracts from
the
* close issues, that are not issues, but questions (they should not
be
in the issue tracker)
* merge duplicate issues
* close issues if issue is already fixed in a released version
* close issues with too little information
Just two thoughts from the top of my head
Matthias
---------------------------------------------------------------------
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
