Thank you Aleksandar for the clarification I was searching for and the link to the foundation's exact plan (I just knew about the intention).
> I don't see anyone willing to spend the time to triage existing bugs in bugzilla and migrate them to GH issue when they make sense. Transitioning everything makes no sense as it will recreate unmanageable pile in GH issues. So new issues should go to GH issues, work on existing ones continue using bugzilla till there is anything that makes sense and there is someone to look at bz issues still.
This is not ideal but the only possible solution right now IMHO. Of course, things can always be done far better in theory but reality puts a lot of other constraints on us.
Sounds like a reasonable plan.
When it's time to close the corresponding Bugzilla-project the migration process used for m2e and Tycho was IMHO good, where all open bugs where closed as "moved" (so similar) with a message informing about the move to GitHub and encouraging involved people to migrate the Bug to the corresponding Github-repo, if the bug is still relevant. This way the reporter of the bug or any one involved could carry out the triage and it had not to be done by only very few persons.
Gesendet: Samstag, 26. März 2022 um 10:38 Uhr
Von: "Aleksandar Kurtakov" <akurtako@xxxxxxxxxx>
An: "Eclipse platform general developers list." <platform-dev@xxxxxxxxxxx>
Betreff: Re: [platform-dev] Intended Bug-Tracker for Platform-projects hosted on GitHub
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.
I don't see anyone willing to spend the time to triage existing bugs in bugzilla and migrate them to GH issue when they make sense. Transitioning everything makes no sense as it will recreate unmanageable pile in GH issues. So new issues should go to GH issues, work on existing ones continue using bugzilla till there is anything that makes sense and there is someone to look at bz issues still.
This is not ideal but the only possible solution right now IMHO. Of course, things can always be done far better in theory but reality puts a lot of other constraints on us.
_______________________________________________
platform-dev mailing list
platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
--
Aleksandar Kurtakov
Red Hat Eclipse Team
_______________________________________________ platform-dev mailing list platform-dev@xxxxxxxxxxx To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
