Re: auto-comment on bugzilla when making an MR?
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
Re: auto-comment on bugzilla when making an MR?
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. Best regards; -- Filipe Saraiva http://filipesaraiva.info/
Re: auto-comment on bugzilla when making an MR?
On 5/20/20 9:44 AM, Luigi Toscano wrote: 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. This process will require time for sure, and some of the changes may not be applied at all as not in line with the general way the system works (and also the our internal changes to support it). In the meantime, having the MR published in a bugzilla comment, and any other integration mechanism, is surely welcome. For sure! I'm just saying, we shouldn't expect or plan to never move to GitLab issues. The proposal in this thread is just one of many things that we'd get for free if we were using it. The pressure to migrate will only grow over time. Nate
Re: auto-comment on bugzilla when making an MR?
Nate Graham ha scritto: > 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 It's all about the right level of integration. > > 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. This process will require time for sure, and some of the changes may not be applied at all as not in line with the general way the system works (and also the our internal changes to support it). In the meantime, having the MR published in a bugzilla comment, and any other integration mechanism, is surely welcome. -- Luigi
Re: auto-comment on bugzilla when making an MR?
Nate Graham ha scritto: > 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 It's all about the right level of integration. > > 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. This process will require time for sure, and some of the changes may not be applied at all as not in line with the general way the system works (and also the our internal changes to support it). In the meantime, having the MR published in a bugzilla comment, and any other integration mechanism, is surely welcome. -- Luigi
Re: auto-comment on bugzilla when making an MR?
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. Nate
Re: auto-comment on bugzilla when making an MR?
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. -- https://www.krita.org
Re: auto-comment on bugzilla when making an MR?
I like the idea, but I hope in future we use Gitlab issues as our tool for bug management. :) Em 20/05/2020 07:13, Harald Sitter escreveu: > Salut! > > Does anyone think it'd be a worthwhile investment to have some piece > of tech automatically comment on bug reports when someone posts an MR > on invent? > > I pretty much never bother posting comments with the MR but at the > same time I know that at least the Plasma team decided to actively use > the Assigned state for bugs. > So I was thinking that it'd perhaps make sense to have automatism in > place that makes sure MRs get referenced in their related bug report > and that the bug is switched into assigned state since it is clearly > being worked on. > Should the MR fall by the wayside for whatever reason a future dev who > happens upon the bug report can at least look up the MR and move it > forward. And using the Assigned state in general seems smart to > prevent multiple people from working on the same thing. > > Thoughts? > > HS > -- Filipe Saraiva http://filipesaraiva.info/
Re: auto-comment on bugzilla when making an MR?
On Wed, May 20, 2020 at 12:13 PM Harald Sitter wrote: > > Salut! > > Does anyone think it'd be a worthwhile investment to have some piece > of tech automatically comment on bug reports when someone posts an MR > on invent? > > I pretty much never bother posting comments with the MR but at the > same time I know that at least the Plasma team decided to actively use > the Assigned state for bugs. > So I was thinking that it'd perhaps make sense to have automatism in > place that makes sure MRs get referenced in their related bug report > and that the bug is switched into assigned state since it is clearly > being worked on. > Should the MR fall by the wayside for whatever reason a future dev who > happens upon the bug report can at least look up the MR and move it > forward. And using the Assigned state in general seems smart to > prevent multiple people from working on the same thing. > > Thoughts? > > HS +1 sounds like a good idea! Like Kai I also try to inform bugs, but I sometimes forget. Aleix
Re: auto-comment on bugzilla when making an MR?
I think bug reporters would like this a lot, as they are then informed that their issue is being worked on. And it would be convenient for the people managing the bugs for a certain product as well. On woensdag 20 mei 2020 12:13:18 CEST Harald Sitter wrote: > Salut! > > Does anyone think it'd be a worthwhile investment to have some piece > of tech automatically comment on bug reports when someone posts an MR > on invent? > > I pretty much never bother posting comments with the MR but at the > same time I know that at least the Plasma team decided to actively use > the Assigned state for bugs. > So I was thinking that it'd perhaps make sense to have automatism in > place that makes sure MRs get referenced in their related bug report > and that the bug is switched into assigned state since it is clearly > being worked on. > Should the MR fall by the wayside for whatever reason a future dev who > happens upon the bug report can at least look up the MR and move it > forward. And using the Assigned state in general seems smart to > prevent multiple people from working on the same thing. > > Thoughts? > > HS > -- https://www.krita.org
auto-comment on bugzilla when making an MR?
Salut! Does anyone think it'd be a worthwhile investment to have some piece of tech automatically comment on bug reports when someone posts an MR on invent? I pretty much never bother posting comments with the MR but at the same time I know that at least the Plasma team decided to actively use the Assigned state for bugs. So I was thinking that it'd perhaps make sense to have automatism in place that makes sure MRs get referenced in their related bug report and that the bug is switched into assigned state since it is clearly being worked on. Should the MR fall by the wayside for whatever reason a future dev who happens upon the bug report can at least look up the MR and move it forward. And using the Assigned state in general seems smart to prevent multiple people from working on the same thing. Thoughts? HS
