[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [platform-dev] Intended Bug-Tracker for Platform-projects hosted on GitHub
|
Speaking from someone who only recently made a first contribution
to Eclipse, but has been using Eclipse for years and occasionally
reported issues, I have to say that already the many existing
project are simply confusing to pick from when a user simply wants
to report something. The bugzilla seems to have the option to
later (re)assign it to the correct subproject.
This doesn't get better with all the different
eclipse-subprojects hosting their own github-projects with
separate issue trackers, as you can't move issues from one
github-project to the other, right? It's also lacking an
integrated overview of issues that might be related, but affect
different subprojects.
So I'd favour something that can provide overarching, integrating
capabilities - be it bugzilla, or something else.
Dirk
Am 26.03.2022 um 09:42 schrieb Hannes
Wellmann:
At the moment it is not clear to me (maybe I have missed
something) if I should still use Bugzilla or instead the
Github Issues of for Eclipse-projects that were moved to
Github?
IIRC to was not the plan to shutdown the associated
Bugzilla now, but does this also mean that bugs should still
be reported there or should GH issues be used for that as soon
as a project was moved?
At the moment I have the impression both is used, which is
IMHO not ideal but probably hard to avoid in a transition
phase.
Thanks,
Hannes
_______________________________________________
platform-dev mailing list
platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev