3 This is a template on how to do a release.
7 On crater branch the repo:
9 cd /repository/git/dragonfly.git
10 git branch DragonFly_RELEASE_x_y (e.g. 2_8)
12 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.
18 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).
20 vi sys/conf/newvers.sh
22 Edit BRANCH, use 'RELEASE', update version. e.g. RELEASE_2_8
28 Edit \__DragonFly\_version and related comments.
30 vi sys/conf/newvers.sh
32 Edit BRANCH, use 'DEVELOPMENT', update version.
36 Make sure all changes on the master branch and on the new branch have been committed and pushed before tagging anything.
38 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.
42 git tag -s -m "DragonFly 2.x.x" v2.x.x
47 git tag -s -m "DragonFly 2.x.x" v2.x.x
50 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.
54 Adjust bulk builds to the release's pkgsrc branch, and make sure they upload to the right directories on avalon.dragonflybsd.org.
56 Adjust the default pkgsrc checkout in /usr/src/etc/Makefile.usr for both master and the new branch if necessary.
59 ###build isos and imgs
61 ###build pkgsrc packages
65 i386 iso, img, gui-img
66 x86_64 iso, img, gui-img
71 installing, encrypted, unencrypted, ufs, hammer
73 configuring in the installer
75 booting installed system
77 testing on real hardware, qemu, vmware
79 ###write release notes
81 ###copy to mirror master