RFC: Suggestion for workflow on patches

[Patrick Winnertz]

Hey,

As there is currently no real written down workflow for patches I would like to 
suggest the following:

 - Every patch which should be applied to the git should be attached to a 
bugreport in our ticketsystem. There should be for each patch a own ticket so 
that we have a good overview.
 -  Every patch that is in the ticket system must be approved by two devs in 
order to get applied again the working branch (master). 
 - If someone dislikes a patch he should either contact the author of the 
patch in order to get a updated version (which should again be added to the 
same bugreport) or fix it himself. In both cases again two developers should 
give their okay to this patch. 

This system makes it possible that everytime a patch should be applied to mc 
at least three people had a look on it (the submitter and two other 
developers). 

As every comment in the ticketsystem from trac is send to the mailinglist it 
should be possible to track things while reading the mailinglist. A feature I 
will add in some time is that you can answer to the ticketmails and the 
automatically get added to the ticketsystem of trac, but this doesn't work 
right now.


What do you think? Is this workflow for patches okay? If yes I would write this 
down somewhere in the wiki in order to make it official.  

-- 
 . '' ` .   Patrick Winnertz <winnie at debian.org>
:  :'   :   proud Debian developer, author, administrator, and user
`. `'`     http://people.debian.org/~winnie - http://www.der-winnie.de
  `-  Debian - when you have better things to do than fixing systems
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.midnight-commander.org/pipermail/mc-devel/attachments/20081230/c9fa0997/attachment.asc>