[Koha-devel] Moving to Arch?

[Paul POULAIN]

MJ Ray a écrit :

>> The commands I used to build the mirror are listed in the above blog 
>> entry.
>
> That's not a mirror. That's your own local branch. You can do some 
> work, commit it and tell me to merge it. You can branch it and 
> generally moosh it about how you want. (One request: don't make more 
> than one archive with the same name, else I may go nuts later.) 
> Imagine having your own local CVS copy of koha that you have total 
> admin control over. You can put more than one branch in each archive, 
> too, which is what koha2--release2-0.2 will be.
>
> Mirrors are created by the archive-mirror command, but I think they're 
> not very interesting other than for distributing files around the 
> world, or publishing a local archive to a public site.

I've begun reading the arch tutorial in french (nice language to read ;-) )
I've a question and this message reminds me it.
You say : "You can do some work, commit it and tell me to merge it". 
iiuc the tutorial and your message, it means you can't have X 
developpers working on the same "branch". The release manager has to 
pick commits from various coders ?
If i'm right, then don't you think it's a big task for the release 
manager ? I find nice to have "cvs update" to get all developpers code, 
and, with the help of the cvs-mailing list, see what has been commited.
Isn't there a way to reproduce CVS behaviour for this : the commit is 
transmitted automatically to the release manager (& other local copies)

-- 
Paul POULAIN
Consultant indépendant en logiciels libres
responsable francophone de koha (SIGB libre http://www.koha-fr.org)