On Tue, May 31, 2011 at 4:31 PM, Happy-melon happy-melon@live.com wrote:
"Brion Vibber" brion@pobox.com wrote in message news:BANLkTinZzef=oRVuw9dWiCVAHYBUWXniqg@mail.gmail.com...
Sing it, brother! We're getting *some* stuff through quicker within the deployment branches, but not nearly as much as we ought to.
The fact that some things are *not* getting stuck in the CR quagmire is part of the *problem*, not the solution. The upper levels of the developer hierarchy ***obviously know*** that the mainline CR process is substantially broken, BECAUSE ***THEY'RE NOT USING IT*** FOR THINGS THAT ARE IMPORTANT TO THEM.
That's not correct -- the same code review tools are being used to look over and comment on those things, AND THEN THE DAMN THING ACTUALLY GETS MERGED TO THE DEPLOYMENT BRANCH BY SOMEBODY AND PUSHED TO PRODUCTION BY SOMEBODY.
It's that step 2 that's missing for everything else until the accumulated release pressure forces a system-wide update.
The unavoidable implication of that observation is that the work of
the volunteer developers *DOESN'T* matter to them. Whether or not that implication is correct (I have confidence that it's not) is irrelevant, the fact that it's there is what's doing horrible damage to the MediaWiki community.
-- brion