[cvsacl-users] How Stable is CVS ACL

[<bit...@gm...>]

Hello everybody,

I'm new to cvs and got a few questions for a project in my company.
I'm looking for a way to manage access a CVS repsitory with differnt user 
permissions to the files and directories on linux. Searching in google 
haven't brougt good ideas to me.
CVS uses in fact, to manage access the file permissions of the file system and 
optionally, the permissions in writers and readers if you have set them. 
The bad thing is, that I cannot do some finetuning on the system.
When I have 5 Projects, for example with 5 different groups I cannot give an 
user which belongs to project1 group write access to the project2 directory 
which belongs to a other group without the option that the other members of 
project1 group cannot access project2 dir.
First I thought, I can solve this problem with the use of the posix acls in 
ext3. But in my tests a cvs commit with pserver of a modified file changes 
the the owner and group of the file to the user id and group I do the commit.
The attributes which I set before with setfacl are lost then after commit. 
And finally I haven't find a way that CVS keep the file permissions and 
uid.gid  on commit as they are in the repository. :-(

So I think the use of CVSACL would be the best way to manage the 
Repository.  ;-)
But why is CVSACL only a patch and is not included in main cvs?
Is it in time more testing, or can it be use in a productive enviroment? 
For examle on a cvs server in company without the risk of loosing data or 
server crashing.
I know it's Offtopic but are there other ways for a flexible access managment 
for a CVS repository?
I would be glade for any help and answers, cause I don't know what I should do 
else or where I can look for a answer.

Best regards

Frank