Release(FHist)

NAME
How to release a version of FHist

CHECKLIST
This document describes the steps involved in issuing a new release of FHist. 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 fhist.51.19, then you would say % aede -p fhist.51 19 % aerpass -p fhist.51 19 % aeib -p fhist.51 19 % aed -p fhist.51 19 % aeb -p fhist.51 19 % aet -p fhist.51 19 % aet -reg -p fhist.51 -c 19 % aeipass -reg -p fhist.51 -c 19 % At this point, branch 19 if project fhist.51 is completed. Cut a new branch, as follows % aenbr -p fhist.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 fhist.51.20 is ready for use. If you want a major version number increment, the process is similar, however you must also terminate the fhist.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 fhist.51 19 et al, to complete aede -p fhist 51 et al, to complete aenbr -p fhist 52 aenbr -p fhist 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.

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

  Update Primary Archive
Transfer a copy to fhist.sourceforget.net by scp. Use the following commands % aecd -bl archive % PLASTICFS=`aesub -bl 'viewpath ${split : $sp}'` \
    LD_PRELOAD=libplasticfs.so \
    /usr/bin/rsync --rsh=ssh \
    -l -r -t -z --stats --delete \
    --progress --exclude '*,*' -v \
    `aegis -cd -bl archive` \
    fhist.sourceforge.net:/home/groups/f/fh/fhist/htdocs/. %

And also transfer the Aegis project tree... #!/bin/sh # # Sync this directory tree with fhist.SourceForge.net # /usr/bin/rsync --rsh=ssh -l -p -r -t -z --stats \
        --exclude bin \
        --exclude archive \
        --exclude linux-i486 \
        --exclude "*.[ao]" \
        --exclude "*.[ch].d" \
        --exclude "*.so.d" \
        --exclude "*.gen.[ch]" \
        --exclude "*,*" \
        --exclude ".cook.fp" \
        --exclude aegis.log \
        --exclude doxygen-html \
        --delete \
        --delete-excluded \
        --progress -v \
        `aegis -cd -bl .. -p fhist` \
        fhist.sourceforge.net:/home/groups/f/fh/fhist/fhist/. But this is all in a shell script to reduce typing, so all you need to do is % aecd -bl .. -p fhist % ./rsync-sourceforge %

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 fhist-.tar.gz 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/fhist/ and click the Admin link, and the Edit/Release Files link, and the [Add Release] link. In the "New Release Name" box put the version number (dumb, huh?). In the "Paste The Notes In" box type
    http://fhist.sourceforge.net/download.html
In the "Paste The Change Log In" box type
    http://fhist.sourceforge.net/ChangeLog
And then finish the rest of the rather cumbersome dialog gunk.

  Notify Mailing List
Send a notification to the fhist-users@lists.sourceforge.net list. It should look like this: To: fhist-users@lists.sourceforge.net Reply-To: pmiller@opensource.org.au Subject: FHist - file history tool
I am pleased to announce that FHist is now available.

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

For information about what new features are available in this release, please see the README file available at the above site.

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 ``fhist'' as there is already an application record.