Re: Stopping daily bump of version.c on old/closed branches

["Joseph S. Myers" <jsm28 at cam dot ac dot uk>]

On Wed, 23 Apr 2003, Daniel Berlin wrote:

> In this case, it looks like we would be changing
>   BRANCHES=`$CVS status -v gcc/ChangeLog \
>                | awk '{print $1;}' \
>                | egrep 'gcc-[0-9]+_[0-9]+-branch$'`
> 
> to something like
>   BRANCHES=`cat gcc/active-branches` \
>                | awk '{print $1;}'
> 
> (or whatever)
> if we were to use a list of active branches.

Extracting the branches from CVS rather than maintaining a list manually
in the crontab was considered an improvement as it reduced the number of
steps required in the branch creation process
<http://gcc.gnu.org/ml/gcc/2002-02/msg01588.html>.  So, if you want to
maintain a list of active branches (maintainer-scripts/active-branches -
maintainer-scripts being checked out in ~gccadmin/scripts, albeit that at
present cvs update needs to be run there manually after changes and the
new crontab installed manually after changes), create a gcc_branch script
to handle most of the branch creation process (including updating
active-branches).  (Closing a branch would be a much simpler process, just
removing the line from active-branches and updating the home page list of
branch status.)

(Of course a gcc_branch script would need testing - an rsynced repository
copy is probably the simplest way of doing that testing.)

Various bits of releasing.html could also be automated that aren't at
present (whether in gcc_release or in a separate script).

-- 
Joseph S. Myers
jsm28 at cam dot ac dot uk