Release()

NAME
How to release a version of

CHECKLIST
This document describes the steps involved in issuing a new release of . It is a simple procedure, but there is enough to do, and it happens sufficiently rarely, that it was worth writing down.

NEW BRANCH
The version stamping is post-numbered. You decide what major or minor version number you want as you are about to release, not when you start work.

Finish development of the branch in the normal way. For example, if you are working on project .51.19, then you would say % aede -p .51 19 % aerpass -p .51 19 % aeib -p .51 19 % aed -p .51 19 % aeb -p .51 19 % aet -p .51 19 % aet -reg -p .51 -c 19 % aeipass -reg -p .51 -c 19 % At this point, branch 19 if project .51 is completed. Cut a new branch, as follows % aenbr -p .51 20 % The branch number will default. This is OK unless you ever skipped a number - in which case it will back fill which is usually undesirable.

At this point project .51.20 is ready for use. If you want a major version number increment, the process is similar, however you must also terminate the .51 branch, and you may well want to create a branch on the branch, to get back to a two-number version scheme. aede -p .51 19 et al, to complete aede -p 51 et al, to complete aenbr -p 52 aenbr -p 52 0 The purpose of a post-numbered branching scheme is that, at any point, you can cut a suitable bug-fix sub-branch.

  Verify New Branch
Create a new change on the branch you just created, and start development of it.

Update any version numbering files, or create any special release notes files, etc, as required. Much of this can be obtained from Aegis, but not all of it.

Create a new change for the previous branch to preserve the change file of the just-released version. Continuing the above example: % aenf etc/CHANGES.51.19 % bl*/etc/CHANGES.sh .51.19 > etc/CHANGES.51.19 %

  Verify New Branch
The first pass of verifying the release set is to use the % aeb RPM lots of output % command. This builds a RedHat package manager file. It is a fairly vigorous test of the build and install, though highly Linux specific. Fix any problems encountered.

Take the archive/..tar.gz file from the current baseline. Unpack it and verify that it configures and builds on one of the Solaris boxes. There are usually small niggling problems, so fix them and try again.

Then unpack it on some other computer which is in the architecture list in the project config file. Configure, build and test it on this machine.

Find yet another type of UNIX box and try again. AIX or Pyramid are always good torture tests, they are such bad UNIX implementations.

Once you have fixed all of the problems, develop end and integrate the change as normal. This creates the initial baseline for this branch; it will contain the appropriate version numbers for release.

ARCHIVES
Once a viable release is ready, it is necessary to upload it to the archives.

  Update Primary Archive
Transfer a copy to aegis.sourceforge.net by FTP. Use the following commands % aecd -bl archive % scp -r . aegis.sourceforge.net:aegis.web/htdocs/. %

  Update Linux Archive
Transfer a copy to metalab.unc.edu by FTP. Login as anonymous and change to the incoming/Linux directory. Use the following commands % aecd -bl archive % ftp metalab.unc.edu user: anonymous ftp> cd incoming/Linux ftp> binary ftp> prompt ftp> mput -* ftp> quit %

There is no need to send email to ewt@metalab.unc.edu, it will be archived automatically in a day or two (or fifteen).

  Update SourceForge Archive
Transfer a copy to upload.sourceforge.net by FTP. Login as anonymous and change to the /incoming directory. Use the following commands % aecd -bl archive % ftp upload.sourceforge.net user: anonymous ftp> cd /incoming ftp> binary ftp> put -.tar.gz ftp> quit %

NOTIFICATION
Once the archives are ready, you can let folks know its there.

Only send the notifications after the files are actually available at the archive site.

  SourceForge.Net
This is way harder than any sane person expects. Go to http://sourceforge.net and login then go to http://sourceforge.net/projects/aegis/ and click the Admin link, and the File Releases link, and the [Add Release] link (near the bottom of the page). In the "New release name" box put the version number, and click the "Create This Release" button. In the "Paste The Notes In" box type
    http://aegis.sourceforge.net/change_log.txt
And then finish the rest of the rather cumbersome dialog gunk.

  Translation Project
Send a notification to the Translation Project translation@iro.umontreal.ca list. It should look like this: To: translation@iro.umontreal.ca Reply-To: millerp@canb.auug.org.au Subject: -.pot I am pleased to announce that is now available. The tarball may be found at http://aegis.sourceforge.net/-.tar.gz Note that this is read and processed by a robot, so don't worry about the human-friendly language of the other notifications.

Only send this notification after the files are actually available at the archive site.

  Notify Mailing List
Send a notification to the -users@auug.org.au list. It should look like this: To: -users@auug.org.au Reply-To: millerp@canb.auug.org.au Subject: - a project change supervisor
I am pleased to announce that is now available.

Aegis is a transaction-based software configuration management system. It provides a framework within which a team of developers may work on many changes to a program independently, and Aegis coordinates integrating these changes back into the master source of the program, with as little disruption as possible.

You are invited to visit
http://aegis.sourceforge.net/ for a more complete description of what is, and access to the download files.

If you are upgrading, please take the time to read the release notes, which may be found in the README file in the sources, or on the web site at
http://aegis.sourceforge.net/change_log.txt

put your .sig file here

Only send this notification after the files are actually available at the archive site.

  Notify Newsgroups
A variety of newsgroups are relevant to , so notify them that the release is available. To: mail2news@replay.com Subject: - a project change supervisor Reply-To: millerp@canb.auug.org.au Followup-To: millerp@canb.auug.org.au
Newsgroups:
alt.sources.d, comp.sources.d, comp.software-eng, comp.software.config-mgmt, gnu.announce

I am pleased to announce that is now available.

Aegis is a transaction-based software configuration management system. It provides a framework within which a team of developers may work on many changes to a program independently, and Aegis coordinates integrating these changes back into the master source of the program, with as little disruption as possible.

You are invited to visit
http://aegis.sourceforge.net/ for a more complete description of what is, and access to the download files.

If you are upgrading, please take the time to read the release notes, which may be found in the README file in the sources, or on the web site at
http://aegis.sourceforge.net/change_log.txt

insert .sig file here Please note that the Newsgroups: line may not actually wrap, or have spaces around the commas.

  Notify Linux Announce
Send a notification to the comp.os.linux.announce list. It should look like this: To: linux-announce@news.ornl.gov Reply-To: millerp@canb.auug.org.au Subject: - a project change supervisor
I am pleased to announce that is now available.

Aegis is a transaction-based software configuration management system. It provides a framework within which a team of developers may work on many changes to a program independently, and Aegis coordinates integrating these changes back into the master source of the program, with as little disruption as possible.

You are invited to visit
http://aegis.sourceforge.net/ for a more complete description of what is, and access to the download files.

If you are upgrading, please take the time to read the release notes, which may be found in the README file in the sources, or on the web site at
http://aegis.sourceforge.net/change_log.txt

put your .sig file here

Only send this notification after the files are actually available at the archive site.

  Notify Web
•) Notify www.freshmeat.net that a new release of Aegis is available. Search for ``aegis'' as there is already an application record.

• Notify www.cmtoday.com that a new release of Aegis is available.

• Notify davis@lrtw.org that a new release of Aegis is available, he's the Debian package maintainer.

• Notify pr@32bitsonline.com that a new release of Aegis is available.