Re: Release procedures?

From: cppljevans (jcampbell3_at_[hidden])
Date: 2002-01-22 21:20:44

--- In boost_at_y..., "Steve M. Robbins" <steven.robbins_at_v...> wrote:

[snip]
> 
> CVS tags are not a limited resource!  Just keep adding
> release candidate tags as necessary, but never move or remove them.
> 
> As a bonus, this scheme allows you to answer the question, "what
> changed between RC4 and RC6?" using CVS.
I apologize if the following sounds naive.  I've only used RCS.
What about recording in a simple text file the versions used
in each release.  For example, for each release of a product, 
record in the simple text file, <product>.release.log, the
text something like:

  1.40 Makefile
  1.2 basic_targets.imk
  1.4 build_variants/gcc/compile_link_commands.imk
  1.2 build_variants/gcc/compile_patterns.imk
  1.10 build_variants/gcc/compiler.imk
  1.1 clean_target.imk
  1.4 default.imk
  1.7 compiler_tests/gc_stl_collect_hide/main.multi_inherit_prox.cpp
  1.1 compiler_tests/gc_stl_collect_hide/subj_base.cpp
  1.1 compiler_tests/gc_stl_collect_hide/subj_base.hpp
  1.5 compiler_tests/gc_stl_collect_hide/target.imk
  1.2 compiler_tests/gc_stl_collect_hide/test_subjects.hpp

and version control <product>.release.log.  Then comparing the
differences between different releases would simply involve
comparing different versions of <product>.release.log.