[
Date Prev][
Date Next][
Thread Prev][Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jdt-dev] Strategy for JDT core issues without sufficient info?
|
We use something similar for Tycho as well, from time to time I review
those and if there is still no feedback after a long time (e.g. > half a
year) I close them with a message to please reopen if the problem still
persist.
Beside that, it is often not easy for *users* to give enough infos as
they don't know, so it can help if someone with deeper knowledge gives
advice *what* info is needed and how to gather that information.
For me, sometimes a stacktrace itself can even help, as one can get some
ideas from the location where the error happens or when one sees a
similar stacktrace later on.
Am 29.03.23 um 19:07 schrieb Andrey Loskutov:
I've created "needinfo" label for JDT core tracker.
Am 29. März 2023 18:49:34 MESZ schrieb S A <simeon.danailov.andreev@xxxxxxxxx>:
Any obvious mark "need info" may at least help us, to not waste too much
time on the same issues time and again.
This is actually my main concern. I don't mind having open bugs that cannot
be worked on yet, but it would be good to filter them out when looking for
something that can be worked on right away (e.g. a reproducer is available).
--
Kind regards,
Andrey Loskutov
https://www.eclipse.org/user/aloskutov
Спасение утопающих - дело рук самих утопающих
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev
