because of Oswald Buddenhagen's post I rethinked the workflow and discussed a 
better workflow with slavaz.

Please comment:
- every patch has to be acked twice
 --> if patch is broken a rev2 has to be created and be discussed
- a acked patch has to be applied in a branch of master and needs to be tested 
there by different people. (Everybody who has tested it should report to the 
- after some testing in the branch we merge into the master branch (and the 
ticket is closed)

This is pretty much the old stuff above (now we create a branch for every 
ticket (proposed branchname 1234_something_describing).

When we want to do a release:

Simply do a tag on mc-4.6.2~rc1 
 --> Test it and if it is okay tag also mc-4.6.2
 --> Otherwise mc-4.6.2~rc2
 --> Test it and if it is okay tag here mc-4.6.2
 --> ...

In the meantime new patches can be discussed and tested as written above.. 
After the release we rebase the branches and merge them into master.

Please comment.


ps:  If this is okay I'll delete the stable branch and update/write a bit 
about this workflow to our wiki)
 . '' ` .   Patrick Winnertz <win...@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

Attachment: signature.asc
Description: This is a digitally signed message part.

Mc-devel mailing list

Reply via email to