El mié., 20 de may. de 2020 a la(s) 18:30, Filipe Saraiva (fil...@kde.org) escribió: > > Em 20/05/2020 12:37, Nate Graham escreveu: > > On 5/20/20 6:50 AM, Boudewijn Rempt wrote: > >> On woensdag 20 mei 2020 14:33:42 CEST Filipe Saraiva wrote: > >>> I like the idea, but I hope in future we use Gitlab issues as our tool > >>> for bug management. :) > >> > >> This has been discussed to death before... The plan is to use the issues > >> to replace phabricator's tasks, not bugzilla. > > > > I'm pretty sure that migrating from Bugzilla to GitLab Issues will > > happen eventually. GitLab Issues has a radically better UI for bug > > reporting and its improved integration with the rest of GitLab will be a > > really nice thing to have. Centralizing everything in GitLab would bring > > real benefits. > > > > Speaking as an extensive bug triager, if it does indeed represent a > > downgrade in terms of organization and workflow, then we will engage > > with the GitLab people to get the issues fixed. They are pretty > > responsive, and it's better than using a dead, unmaintained version of a > > stagnant product. > > > > Sure, in addition this adoption will provide all of these automation we > need to implement to work in different tools, will be less work to > sysadmin team in order to maintain an old product, and more. > > In fact, thinking about "KDE is all about apps" objective, the adoption > of Gitlab issues for bug management is a interesting step. It will allow > the community of a specific project work in more productive way than use > a different tool for that task. > > But well, maybe it is a discussion for the future. >
It's a discussion for months or years in the future. Please, we didn't even finish with this migration. -- Nicolás
