I agree with Alex that we should move to use GH issues for new stuff. Bugzilla can be used for existing issues opened in Bugzilla.
For GH issues is there a way we can have Eclipse top-level milestones like we did in Bugzilla? I was looking into this briefly and it seemed each repository has to define its own milestones to assign to issues. Tom ________________________________ From: platform-dev <platform-dev-boun...@eclipse.org> on behalf of Hannes Wellmann <wellmann.hann...@gmx.net> Sent: Saturday, March 26, 2022 3:42 AM To: platform-dev@eclipse.org <platform-dev@eclipse.org> Subject: [EXTERNAL] [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 ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. ZjQcmQRYFpfptBannerEnd 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@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
