RE: Scenario and applicability of CVS

[Brian G. Peterson]

>From the sounds of it, your development process should be easily adapatable
to CVs using tags.  When a new release is finalized, you set a tag on that
release.  This will allow you to recreate the release at a later point.  A
single version of a file may have multiple tags on it, so files that do not
change very often may have the same version tagged for multiple releases.
you are already using rcs, so you understand branching.  CVS support for
branches is similar to that used by rcs (cvs uses the rcs file format to
store revisions).

Someone else on this list with more experience can probably advise you on
how to import your rcs project into cvs, but it should be pretty simple.

Regards,

   - Brian

> Hi
> I am going to try to briefly sketch the scenario we have and what I
> need is you to tell me whether cvs is able to do what we require. I have
> read a lot of information, but I would like to have real life opinions
> as well.
>
> We have several independent code systems that together is used to
> "produce" one version of our system. This system basically have a
> stable
> version(branch) and a unstable/development version.
>
> Further, if I request version 1 of the system it would consists of the
> various sub-programs/code systems. Typically the version numbers of
> these subsystems would not necessarily correspond. Version1 would
> consist of A1.0 B2.5 and C0.5. Version2 would consist of A1.0 B2.6 and
> C0.6. These subsystems could also change versions by just adding a
> file or editing a file. We dont have many developers so concurrency will
> not be an issue 98% of the time. The developers tend to work on
> different systems anyhow.
>
> Btw
> We are currently using rcs and a few handwritten scripts.
>
> Groete
> --
> Gerhardus Geldenhuis
> System Administrator
> Reactor Theory(NECSA)
> address@hidden
> Mobile +27 83 784 7664
> Office  +27 12 305 5600
>
>
>
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs
>