[Top][All Lists]

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

RE: Issue with identifying scripts within a repository

From: Guus Leeuw jr.
Subject: RE: Issue with identifying scripts within a repository
Date: Tue, 23 Nov 2004 21:12:02 +0100

> -----Original Message-----
> From: address@hidden [mailto:info-cvs-
> address@hidden On Behalf Of Jeeva Sarma
> Sent: mardi 23 novembre 2004 20:18
> To: address@hidden
> Subject: Issue with identifying scripts within a repository
> We have a repository to store scripts which are run
> against databases. When the developers check-in the
> scripts, no one knows if that will go all the way to
> prod. It has to pass qc, or may have some other
> issues, so everything that is checked in may not go to
> prod.
> All approved scripts will run once in 2 months.So we
> need a way to identify all these scripts from the
> others in the repository.Pls note that the number of
> these scripts is very high.

Why don't you handle the scripts with development life cycle?

Test will be a tagged version of the scripts package: V1_0_TEST. This
package goes to Test. Dev will be developed with new features if needed. If
need be, V1_0_TEST will be branched, so that local fixes can be applied.
Once Test is happy, tag that with V1_x_PROD, and move it to prod. At this
point in time, merge the changes on the V1_0_TEST branch back to main stream
development (== HEAD), resolve the conflicts, and develop further.

Just my 2 cents,

Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (
Version: 6.0.788 / Virus Database: 533 - Release Date: 01/11/2004

reply via email to

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