Re: how many patches can we review?

[Janek Warchoł]

2011/8/16 Graham Percival <address@hidden>:
> We're up to 59 patches now, plus 17 patches on the "plz review; no
> known problems" list.  We're losing ground quickly, and this will
> soon become a serious problem for developers and contributors (if
> it isn't already).
> I see three options, none of which fill me with joy.
>
> 1) encourage more pushing without reviews.
> 2) assign certain people to be in charge of certain areas (e.g.
> Carl has final say over anything beaming-related), and encourage
> that person to review+push patches in his area ASAP.
> 3) double or triple the rate of patches in the countdown.
>
> Out of those options, I dislike #3 the least.  I'm thinking of
> having 10 patches per countdown, 48 hours for each countdown.  I
> know that's a lot of reviewing, but if we want to keep the
> opportunity for reviews, that's the kind of workload we need to
> handle.

+1

cheers,
Janek


2011/8/16 Mike Solomon <address@hidden>:
> That said, I find that there is a positive correlation between the amount of 
> my music that gets played / paid / enjoyed and the amount of development I do 
> for LilyPond (I have no clue how this works, as in theory this means I have 
> less time, but oh well!).  So, I don't anticipate stopping my quest to 
> eliminate all collisions[1] from LilyPond in the near future.

:D