They use CVS where I work to keep track of incremental builds within the
software engineering department but released version and revision
numbers are assigned by the configuration management department. We use
CVS tags to keep track of a particular Software Change Request that an
incremental build is based on. The version number has to do with a
particular product line and the revision number has to do with the with
the number of updates, placed under configuration management, to that
software version.
Paul M Foster wrote:
>
> CVS assigns rev numbers on the order of 1.1.2, 1.2.1.1, etc. My
> experience has been that in the process of developing a project I have
> various files of various CVS-assigned revision numbers. When I finally
> get to a release point, I have to figure out a way to know that version
> of 1.1 of this file, 1.3 of that file, etc., all equal my public release
> of "Version 3.2". It seems that assigning cvs "tags" might be a possible
> solution, but tags must start with a letter (not "3.2"). Or you could
> tarball each major public version, but that kinda defeats the purpose of
> CVSing things.
>
> So I'm wondering, in real production environments, how do project admins
> track this and keep everything straight (when using CVS)?
>
> Paul
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 17:46:09 EDT