On Tuesday, 12 September 2017 18:43:00 UTC+2, vdelecroix wrote:
>
> Hi Marteen,
>
> Though in an ideal world
> - tickets should not be merged if any patchbot is not happy with it
>
Hi looked a bit more into this stuff and I think that the main reason why
this happens is that even though we
Hi Vincent,
Thanks for pointing out the point of view from a patchbot maintainer, my
statement "I think a complete burden is highly exaggerated" was made from
my perspective as a developer not knowing how this looks from a patchbot
maintainer point of view. And I can see that having to deal wit
Hi Marteen,
"complete burden" = "each release". So precisely, we need somebody to
volunteer to maintain this list. I already hardly find the energy to
fill a ticket for the reasons why my patchbot is not working any more at
each new release (including the fact that I need to search for a
reas
Hi Vincent,
I think "a complete burden" is highly exaggerated, there should not be a
new patchbot ticket to often. And if someone has to create a ticket then
just copy pasting the failing files and the ticket number to the ticket
description should not be to much work.
As for removing old stuf
Hi,
I think a meta-ticket is a complete burden to maintain. And as already
said in other mails, this identification should be done by other means.
Vincent
On 11/09/2017 18:59, Maarten Derickx wrote:
Hi all,
During the recent writing of new code and reviewing I got annoyed that it
costs real
On 12/09/2017 12:23, Jeroen Demeyer wrote:
On 2017-09-11 18:59, Maarten Derickx wrote:
I think that all patchbot failure tickets should automatically deserve
the status critical.
They should be blockers (unless the error comes from a broken patchbot).
+1
p.s. Tips on how to search for tick
On 2017-09-11 18:59, Maarten Derickx wrote:
I think that all patchbot failure tickets should automatically deserve
the status critical.
They should be blockers (unless the error comes from a broken patchbot).
p.s. Tips on how to search for tickets on trac are welcome!
Google
site:trac.sage
On Mon, Sep 11, 2017 at 12:59 PM, Maarten Derickx <
m.derickx.stud...@gmail.com> wrote:
> Hi all,
>
> During the recent writing of new code and reviewing I got annoyed that it
> costs really a lot of effort for me to see if there was already a ticket
> for a certain patchbot failure. I therefore d
