Re: Multi-tier development CVS plan

[adp]

Did you get a response on this? We are looking to move from a single CVS
branch (MAIN) to either a two- or three-tiered system. Would be happy with
hints.

We are thinking of this:

unstable -> stable -> release

unstable:
This is where our current development goes.

stable:
This is where we merge our soon-to-be-released code so that QA can begin
work.

release:
This is where we merge from stable, tag an official code release, and then
push the release.

Should we rethink how we are going to work this? We are totally open to
other ideas, and haven't settled on anything.

----- Original Message ----- 
From: "Jeraimee Hughes" <address@hidden>
To: "Info-cvs" <address@hidden>
Sent: Wednesday, January 28, 2004 11:21 AM
Subject: Multi-tier development CVS plan


> I'll be modifying our development process here at the office from 3
> tier (development->stage->production) to 4 tier
> (development->stage->release->production) and I'm trying to make sure
> I have the best CVS plan.
>
> Any feedback (good and bad) would be great. I'm not sure if I'm way
> off base here or if I'm starting to zero in on the best plan of
> attack.
>
> Planned:
>
> Development Branch(s)
> ---------------------
>  All development takes place in development branches.
>  Branching from this branch is permitted for larger clients
>  e.g. create a YOYO branch for custom coding for YOYO
>
>  ----
>      \DEV
>       ---
>          \YOYO
>           \FOO
>
> Stage Branch
> ------------
>  This branch will be all ready development branches merged for QC and
>  final testing based on dates/release schedules.
>
>   ---------
>   \DEV     \STAGE
>    ---
>       \YOYO
>        \FOO
>
> Release Branch
> --------------
>  The release branch will always be a current checkout of the same code
>  on production systems, again based on dates/release schedules.
>
>   ------------------
>   \DEV     \STAGE   \RELEASE
>    ---
>       \YOYO
>        \FOO
>
>
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs
>
>