removal of submaster

Hi,

as discussed on irc, I want to ask to replace submaster.

Reasons:
 - Patches get applied only rarely, like half-year-wise. They are updated two or
 more times while lingering in the web-frontend, sometimes don't apply anymore
 or just with manual fixes, and more negative implications of aged patches.
 - devs that use submaster and have applied patches locally regularly get into
 synchronization troubles when the master trunk applied patches after a long
 time, due to the fixes that the application procedure made necessary.
[add your reasons here]

Replacement:
 1. experimental subversion branch, that is accessible for (web-)registered
 users. This almost the same as the submaster webinterface, but much more
 comfortable to use. 
 Patches are merged to the stabilization-trunk after a  regression test. 
 Votes can be stored in subversion properties
 2. git (blindcoder?)
 [add other suggestions here]

Background:
I am a quite calm and lazy person. I continued using submaster, although it
imposed usability regressions. It had made many ROCK developers already leave
the project in favour of a fork. My reason for not switching was mainly the
uncomfortable explosive ego of the fork's leader. From what I hear, I am not the
only one that feels that way.
We should change something, in a way that it pleases the _majority_ of the
remaining dev's. Otherwise I fear ROCK will continue to peter out and die due
to lack of vital ressources - developers.

Ciao

Andreas

_______________________________________________
rock-devel mailing list
[email protected]
http://www.rocklinux.net/mailman/listinfo/rock-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFD7I+e2A9/vRi9PS4RAiptAJ0aK8NhpL5cZxRY1RR1EzfO93nBBgCfSXei
K77WUxp49Hzz58hh+r20Uco=
=DspH
-----END PGP SIGNATURE-----