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 Gitl
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.
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, unmainta
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 u
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 u
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'
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.kr
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
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
> sa
Good idea!
I often post a Phabricator patch links on a bug report to ask the bug
reporters to test and see if it fixes the issue for them, too.
It also shows the reporter and other members of the team that someone
already triaged the issue or it is already being worked on.
Cheers
Kai Uwe
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 b
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
th
12 matches
Mail list logo
