Automating the NonResponsiveMaintainers policy
"Jóhann B. Guðmundsson"
johannbg at gmail.com
Fri Mar 2 12:13:12 UTC 2012
On 03/02/2012 11:47 AM, Marcela Mašláňová wrote:
> Some developers prefer ignore it until they have time. Why should I
> write yes, yes, it's broken, I'll look at it next month. That's not
> helping anyway.
I disagree it certainly does matter.
For example let's take these two   bugs that are on my components
list for my feature.
Bug 1 was filed 2011-11-16 and has absolutely no comments.
Which leaves me wondering..
A) is this package being actively maintained?
B) Is it planned for removal?
C) Is there something wrong with the submitted unit file?
D) Are upstream changes necessary for this component to be migrated?
E) Is it safe to flag the component to be package by proven packages?
Now let's look at bug 2 was also filed 2011-11-16 and has one comment
from the maintainer which came 3 days later.
"Thanks, I'll test and apply it. Hoping to actually fix the deamon too."
Now I have the answer to A,B,C,D,E.
For bug 1 I have to initiate non responsive maintainers policy which
takes 3+ weeks to finish....
For bug 2 I can just ping him with status if he has not yet packaged the
submitted unit no later than week before the deadline to ship units comes.
So as you can see responses do indeed matter.
More information about the devel