[development] What about reviewing patches?

Marcel Partap mpartap at gmx.net
Wed Aug 13 19:01:16 UTC 2008

Ryan Cross wrote:
> Maybe speed of commitments isn't the key problem, but avoiding loosing
> tester's motivations is something to consider. Or tackle the
> committers speed if that is the underlying problem. Ideas?
Mhh.. what about (auto-)committing to a D7.x-next branch after two 
independent people have confirmed a patch as working? That would give the 
process of reviewing patches more resoluteness, also liberating the core 
CVS admins to decide what gets in and what not. Patches that don't proof as 
a problem in 7.x-next could then be cherry-picked to 7.x-dev... Of course 
this would make running the next-branch a risky business, but at least it 
helps getting out of the situation where perfectly good and simple patches 
are not applied for weeks and months because the concerning code is being 
completly rewritten on some other issue (module system revamp f.e.)...

  "Obstacles are those frightful things you see when you take
   your eyes off your goal."         -- Henry Ford (1863-1947)

   Change the world! Vote revolution: http://hfopi.org/vote-future

More information about the development mailing list