>> Finally finding time to go over this. In the future I want to have more time 
>> to
>> review such massive series, as it causes severe stress to be forced to review
>> this last minute before it goes upstream.
>>
>> So if I push back in order to give me some more room to breathe in the future
>> it's nothing personal, I just have to keep my sanity somehow.
>>
>> I hate being forced to review because we pick up stuff way to early. There is
>> just way too much other stuff going on.
>>
>> I'm planning on picking up most stuff I maintain in the next cycle. For
>> cross-component stuff (esp. VMA) I expect Andrew to pick stuff up until we
>> tackle this once cycle later.
> 
> OK I understand, sorry for sending such a large series.

Just to be clear, this is not your fault.

> 
> I already delayed it from last cycle and sent early in rc2, but I understand
> there's been a lot of volume in this one.
> 
> I've been working evenings and weekends myself to keep up with review (and
> failing), so I get how thankless it can be (LPC was also unhelpfully timed!)
> 
> I will try to split things out more in future, this had a lot of dependencies 
> so
> it wasn't clear that made sense + wouldn't just cause more stress over a 
> longer
> period otherwise.

I think it's really the people that do all of the review+maintanance work that
should decide *when* something is ready.

Some stuff simply takes longer than a cycle. If it's due to conferences,
bugreport/fixes, high volume of others things, (transition work) or anything
else (personal etc.).

And that's ok.

There is barely a difference between squeezing something into this release vs.
queuing it early in the next release.

Well, there is a difference: making David's head shoot steam out of both ears.

I'm hoping the merge window will actually give us time to do exactly that: focus
on the things that didn't make it in time and just finish them.

That's what I'll be doing with Usamas patches and some of Riks stuff next.

[...]

> 
> I will split it out into another patch.

Thanks!

-- 
Cheers,

David

Reply via email to