[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to structure my project?

From: Matthew Riechers
Subject: Re: How to structure my project?
Date: Thu, 12 Jul 2001 09:41:57 -0400

Garvin Hicking wrote:
>  Salutations, info-cvs!
> I have to manage a project with multiple users. This project is a PHP-
> Website with some graphics and mostly textpages.
> I use the CVS-downloaded code as well on our production machine as on our
> testing machines.
> The project has to be structured to contain a maintainable beta-version
> and the final-version. The final-version always has to be a stable release
> and must be editable at any point without too much problems (for
> hotfixing...common problem on a PHP-website, I think). All users have to
> use the beta-version for integrating new features. It is necessary, that
> these new features are accessable for any user, so they can't be only
> developed in a working directory.

Take a look through Karl Fogel's book for some excellent coverage on
repository management <>

I would use the current trunk for your 'beta', and simply tag the tree
when you've reached a milestone along the way. If you need to change
something later starting at a tagged point, do the branch and merge the
changes back into the trunk if needed. To maintain 'current' and
'stable' directories, just 'cvs up' on "current" and 'cvs up -r
MILESTONE_X' on "stable".


reply via email to

[Prev in Thread] Current Thread [Next in Thread]