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 check-tarball lots of output % command. This builds The tarball, and then unpacks it and builds Aegis from scratch. 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 change. Try it out on as many different architectures as you have access to. Try as many of these as you have access to: various Linux distributions (including AMD64), various BSD distributions, various Solaris versions, MacOSX, AIX, HP/UX, SGI. Some are such bad implementations of Unix that you will almost always find something.

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
The aeb check-tarball step, above, produces a bunch of files suitable for installation on SourceForge to as the CGI interface. This serves a s a demo of Aegis' distributed development facilities, and is also used by Aegis developers for just this use. Upload the aegis-sf.tgz file and unpack it % scp aegis-sf.tgz aegis.sourceforge.net:. % ssh aegis.sourceforge.net blah blah %

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

You also need to update the SourceForge download servers. This is best done by using FTP from aegis.sourceforge.net to upload.sourceforge.net as this is a fast internal SourceForge network transfer, and not a slower through-the-cloud transfer.

  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> put -.rm.pdf ftp> put -.ug.pdf ftp> quit %

NOTIFICATION
Once the archives are ready, you can let folks know it's 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 robot@translationproject.org list. It should look like this: To: robot@translationproject.org 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 Web
•) Notify www.freshmeat.net that a new release of Aegis is available. Search for “aegis” as there is already an application record.

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