#The art of releasing

This is a template on how to do a release.

##Branching

On crater branch the repo:

    cd /repository/git/dragonfly.git
    git branch DragonFly_RELEASE_x_y        (e.g. 2_8)

This is the only step that needs to happen remotely.

On your own system:

Check out two copies of /usr/src, one with master checked out, one with the new release branch checked out.  Checkouts should be under your user id, NOT as root, or the later tagging operation will be unhappy.

On the new branch:

    vi sys/sys/param.h      

Edit \__DragonFly\_version and related comments.  Be sure to add a comment for the new master too (but the version is set to the new release).

    vi sys/conf/newvers.sh  

Edit BRANCH, use 'RELEASE', update version.  e.g. RELEASE_2_8

On master

    vi sys/sys/param.h

Edit \__DragonFly\_version and related comments.

    vi sys/conf/newvers.sh  

Edit BRANCH, use 'DEVELOPMENT', update version.

##Tagging

Make sure all changes on the master branch and on the new branch have been committed and pushed before tagging anything.

man git-tag for info, the committer needs GPG set up so git tag -s works.  Then you can use your own checkout.  Be sure the checkouts are under your user id and you do the tagging as yourself instead of as root.

###In master

    git tag -s -m "DragonFly 2.x.x" v2.x.x
    git push --tags

###In the new branch

    git tag -s -m "DragonFly 2.x.x" v2.x.x
    git push --tags

Do the x.x.0 immediately.  Just before doing the final nrelease build roll a x.x.1 tag for the release branch.  Release as x.x.1.

## Subsequent tag updates

When updating a x.x.1 version, you just need to edit sys/sys/param.h in the appropriate branch and then tag.

## Something in GCC

The file gnu/usr.bin/cc41/cc_prep/config/dragonfly.h has a spot where the major version number for DragonFly is encoded.  I don't know if this applies for anything other than gcc 4.1.

    #define        DFBSD_MAJOR     3

This comes from John Marino's commit:

<http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/43add724990da155c21ef4a0893f4ebc2c36eb05>

##Pkgsrc 

Adjust bulk builds to the release's pkgsrc branch, and make sure they upload to the right directories on avalon.dragonflybsd.org.

Adjust the default pkgsrc checkout in /usr/src/etc/Makefile.usr for both master and the new branch if necessary.

###build isos and imgs



###build pkgsrc packages

###testing

i386 iso, img, gui-img
x86_64 iso, img, gui-img


booting install media

installing, encrypted, unencrypted, ufs, hammer

configuring in the installer

booting installed system

testing on real hardware, qemu, vmware

###Release Notes

Copy one of the existing release pages.  The general format is :

* General announcement
* Big items new to this release
* Availability, describing what can be run
* MD5 results for compressed and uncompressed files
* Special notes and caveats
* Release notes - go through git log for these.

###File Copy

Place images in /ftp/iso-images on crater.dragonflybsd.org.  They will be rsynced to mirror-master.

###announce
users@, web page