Controlling source code

[Neil Watson]

I think that using ACLs and manual scripting is the hard way to do this.
Perhaps using something like Subversion? Any suggestions?

Purpose
To control the flow of software packages from pre QA work through to GA.

Requirements
Packages, but not documentation, will be moved by the packaging team to
the pre-QA vault (PRQA). Access rights to PRQA allow the packaging team
to add new content but, not change or remove existing content.

The PRQA vault is available internally to others outside of the
packaging team, on a read only basis. Install systems will be able to
point their installers to the PRQA via NFS.

The PRQA vault will be mirrored to another hard drive for safety.

Once a package is ready to pass from PRQA to post QA (POQA), the
relevant files will be moved, by IT, to the POQA vault. Once in POQA the
files will be read only to all users. As with the PRQA these files will
be available via NFS.

Technological Considerations.
Granting the required access rights for PRQA will likely require the use
of linux ACLs.

Given the large amount of data to be stored and moved on this system,
SATA drives should be used.

Since this system will have a large capacity and host many large files
the XFS file system should be considered over ext3.

-- 
Neil Watson               | Gentoo Linux
Network Administrator     | Uptime 16 days
http://watson-wilson.ca   | 2.6.11.4 AMD Athlon(tm) MP 2000+ x 2
--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml