On Sat, Mar 26, 2022 at 10:42 AM Hannes Wellmann <wellmann.hann...@gmx.net> wrote:
> 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? > Use GH issues once repo moved. There is no plan to shutdown bugzilla immediately from our side as there is way too much content in it and even valid bugs . But foundation plans to do so see https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Gerrit/Gerrit-and-Bugzilla-deprecation-and-migration-plan so there is no other choice . > 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. > > Thanks, > Hannes > > > _______________________________________________ > platform-dev mailing list > platform-dev@eclipse.org > 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@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
