Skip to main content
[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
Instead of creating more and more repositories, it would be better to simply merge them to meaningful units.
Then one could simply create an organization readme where it explains what problems should be reported to what sub project... 

As one at the moment has to chose a component as well in bugzilla.

Am 26.03.22 um 12:22 schrieb Hannes Wellmann:
It is possible to move issues between repositories on GitHub, see [1], and it is also possible to link issues in other repositories by mentioning them. Although it is simpler for those that handle bugs to assign them to the correct repository directly, I agree that it can be difficult to find out which one the correct repo is, especially if one is not deeply involved into Eclipse development. To help those people maybe it would be useful to create a repo at https://github.com/eclipse/ide (or similar) that is de-facto empty and where users can report bugs for which they don't know the responsible project/repository for. The bugs could then be transferred to the correct repo by committers that can identify the responsible repository. But I assume there is definitely the risk that managing such a common bug-tracker becomes quite a great task that consumes too many resources. So bug reports should be encouraged to only use it as last resort and there should be good documentation/guidelines for reporters to find the appropriated repo by them self. [1] - https://docs.github.com/en/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository 
*Gesendet:* Samstag, 26. März 2022 um 11:07 Uhr
*Von:* "Dirk Steinkamp" <Dirk.Steinkamp@xxxxxx>
*An:* "Eclipse platform general developers list." <platform-dev@xxxxxxxxxxx>
*Betreff:* 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, visithttps://www.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________ platform-dev mailing list platform-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev <https://www.eclipse.org/mailman/listinfo/platform-dev> 

_______________________________________________
platform-dev mailing list
platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev

Back to the top