This page was produced by an automated import process, and may have formatting errors; feel free to fix.
Cut the Branch
- [Create-the-branch ]
Create the branch
$ u=5.1 $ v=5.2 $ V=`echo $v | sed 's/\./_/g'` $ D=`date -u +%Y-%m-%d` $ echo $u $V $D 5.1 5_2 2002-03-03 $ echo cvs -f -d :ext:sourceware.org:/cvs/src rtag \ -D $D-gmt gdb_$V-$D-branchpoint insight cvs -f -d :ext:sourceware.org:/cvs/src rtag -D 2002-03-03-gmt gdb_5_2-2002-03-03-branchpoint insight $ ^echo ^^ ... $ echo cvs -f -d :ext:sourceware.org:/cvs/src rtag \ -b -r gdb_$V-$D-branchpoint gdb_$V-branch insight cvs -f -d :ext:sourceware.org:/cvs/src rtag \ -b -r gdb_5_2-2002-03-03-branchpoint gdb_5_2-branch insight $ ^echo ^^ ... $
- By using -D YYYY-MM-DD-gmt, the branch is forced to an exact date/time.
- The trunk is first tagged so that the branch point can easily be found.
- Insight, which includes GDB, is tagged at the same time.
version.in gets bumped to avoid version number conflicts.
The reading of .cvsrc is disabled using -f. [Update-version_002ein ]
$ u=5.1 $ v=5.2 $ V=`echo $v | sed 's/\./_/g'` $ echo $u $v$V 5.1 5_2 $ cd /tmp $ echo cvs -f -d :ext:sourceware.org:/cvs/src co \ -r gdb_$V-branch src/gdb/version.in cvs -f -d :ext:sourceware.org:/cvs/src co -r gdb_5_2-branch src/gdb/version.in $ ^echo ^^ U src/gdb/version.in $ cd src/gdb $ echo $u.90-DATE-cvs > version.in $ cat version.in 5.1.90-DATE-cvs $ cvs -f commit version.in
The string ‘DATE’ is used to substitute the checkout date at build time; the date comes from bfd/version.h.
.90 and the previous branch version are used as fairly arbitrary initial branch version number. [Update-the-web-and-news-pages ]
Update the web and news pages
Something? [Tweak-cron-to-track-the-new-branch ]
Tweak cron to track the new branch
The file gdbadmin/cron/crontab contains gdbadmin’s cron table. This file needs to be updated so that:
A daily timestamp is added to the file bfd/version.h.
- The new branch is included in the snapshot process.
See the file gdbadmin/cron/README for how to install the updated cron table.
The file gdbadmin/ss/README should also be reviewed to reflect any changes. That file is copied to both the branch/ and current/ snapshot directories. [Update-the-NEWS-and-README-files ]
Update the NEWS and README files
The NEWS file needs to be updated so that on the branch it refers to changes in the current release while on the trunk it also refers to changes since the current release.
The README file needs to be updated so that it refers to the current release. [Post-the-branch-info ]
Post the branch info
Send an announcement to the mailing lists:
[mailto:email@example.com GDB Announcement mailing list]
Pragmatics: The branch creation is sent to the announce list to ensure that people people not subscribed to the higher volume discussion list are alerted.
The announcement should include:
- The branch tag.
- How to check out the branch using CVS.
- The date/number of weeks until the release.
- The branch commit policy still holds.