I think a stacktrace alone is also valuable, especially if you start counting duplicates. The old error reporting infra used to aggregate such duplicates.
People also won't answer the same day for a follow-up. Because they might be busy. But also because they might have lost interest in that issue/NetBeans. Ideally they should have gotten a reply the same day, while the issue was fresh in their mind. In the end I think having a public issue tracker but providing no quality handling of user reports is just bad marketing. I know for sure I will *never* report a bug to a Gnome project. We don't want people to think the same of Apache NetBeans. If we care about follow up just tell people to report issue on dev@. --emi vin., 16 aug. 2019, 08:43 Tomáš Procházka <ka...@razdva.cz> a scris: > Hi, > I agree with points made by Matthias. > > Yesterday I tried to go through issues without assigned component and > assign at least PHP ones. > > I found a lot of filed bugs containig only stack trace without any > specific steps leading to exception. Requests to provide more specific > information were not answered. I think this type of bugs can be closed > after two months as incomplete. > > With regards, > Tom > > On 2019/08/13 20:23:06, Matthias Bläsing <m...@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 > > > >
