[Linuxcoe-devel] Developing on SourceForge

[Shank, J. R. <js...@hp...>]

Here is the proposed development process:

-----
1. Each developer checks out a sandbox from CVS on SourceForge.
Instructions are found on 
    http://sourceforge.net/cvs/?group_id=144250 
under Developer CVS Access via SSH.

2. Developers make changes to the files and test them on their
development machine. When they are ready to test them on the testing
server (which matches the production environment as closely as
possible), they check them into CVS.

3. Files from CVS head-of-stream are checked out (perhaps by cron) to
the testing server. If possible, relevant regression tests should be
done to ensure the changes do not break anything else.

4. After the changes have been fully tested, the developer tags the
files as "stable". 

5. During the next release phase the stable files in the repository are
tagged with the version number of the release and that release is
exported and tarred for delivery through the SourceForge file server.
The tarball is then downloaded to the production server, extracted, and
installed in the relevant directories with that releases version number
(for example, /*/opt/SysDes/4.0/*). On the release date, symlinks to the
current version are updated to point to the new version.
-----

There will be another e-mail going out sometime tomorrow for the process
on critical bug fixes. Until then, let me know what you think about this
process.

Thanks,
Jeff