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 This is the only step that needs to happen remotely.
16 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.
21 git remote add origin ssh://crater.dragonflybsd.org/repository/git/dragonfly.git
26 # x_y is the release; faster than rechecking out
30 git branch DragonFly_RELEASE_x_y origin/DragonFly_RELEASE_x_y
31 git checkout DragonFly_RELEASE_x_y
37 Edit \__DragonFly\_version and related comments. You only need to add a commented version number for the branch, not the new master.
39 vi sys/conf/newvers.sh
41 Edit BRANCH, use 'RELEASE', update version. e.g. RELEASE_2_8
43 vi gnu/usr.bin/groff/tmac/mdoc.local
45 In the "Default .Os value" section, bump up the version to that of the release (even minor number).
49 Adjust the default src checkout in /usr/src/etc/Makefile.usr to pull this branch. Otherwise, anyone using the Makefile to download source will get master, and nrelease will build master.
55 Edit \__DragonFly\_version and related comments. Put in commented numbers for the new release and master.
57 vi sys/conf/newvers.sh
59 Edit BRANCH, use 'DEVELOPMENT', update version.
61 vi gnu/usr.bin/groff/tmac/mdoc.local
63 In the "Default .Os value" section, bump up the version to that of the master (odd minor number). Additionally, in the "DragonFly releases not found in doc-common" section, add a new line (a la the previous ones) for the new master.
75 Make sure all changes on the master branch **and** on the new branch have been committed and pushed before tagging anything.
79 git add sys/sys/param.h sys/conf/newvers.sh gnu/usr.bin/groff/tmac/mdoc.local etc/Makefile.usr
85 git add sys/sys/param.h sys/conf/newvers.sh gnu/usr.bin/groff/tmac/mdoc.local
90 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.
92 You may need to set GPG_TTY to get GPG to work if it tries to run pinentry-curses. This is the line for bash, since that's quoted most often for this fix.
98 git tag -s -m "DragonFly x.x.0" vx.x.0
103 git tag -s -m "DragonFly x.y.0rc" vx.y.0rc
106 Do the x.x.0rc immediately. Just before doing the final nrelease build roll a x.x.0 tag for the release branch - the same method, just without "rc" for release candidate. Release as x.x.0.
108 A new tag may require a commit beforehand to the release branch to make sure it goes to the right branch.
110 ## Subsequent tag updates
112 When updating a x.x.1 version, you just need to tag.
116 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.
118 #define DFBSD_MAJOR 3
120 This comes from John Marino's commit:
122 <http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/43add724990da155c21ef4a0893f4ebc2c36eb05>
126 Adjust bulk builds to the release's pkgsrc branch, and make sure they upload to the right directories on avalon.dragonflybsd.org.
128 Adjust the default pkgsrc checkout in /usr/src/etc/Makefile.usr for both master and the new branch if necessary.
130 ###build isos and imgs
134 ###build pkgsrc packages
138 Testing should be done on real hardware, qemu and vmware. We have six isos/imgs that needs testing.
140 i386 iso, img, gui-img<br/>
141 x86_64 iso, img, gui-img
145 * Booting install media.
146 * Installing; encrypted, unencrypted, ufs, hammer.
147 * Configuring everything in the installer; try both dhcp and static IP.
148 * Booting the installed system.
152 Copy one of the existing release pages. The general format is :
154 * General announcement
155 * Big items new to this release
156 * Availability, describing what can be run
157 * MD5 results for compressed and uncompressed files
158 * Special notes and caveats
159 * Release notes - go through git log for these.
163 * Update the release page, the main page, and the general [[Download]] page.
164 * Add new MD5 sums on the release page for the compressed and uncompressed files.
168 Place images in /ftp/iso-images on crater.dragonflybsd.org. They will be rsynced to mirror-master.
170 The file md5.txt should have the md5 output for all the compressed files. It should also have the md5 output for the uncompressed images, so don't just 'md5 *bz2 > md5.txt'; get that separately and copy it into the document.
172 /root/adm/domd5.sh will get the MD5 sums for the compressed and uncompressed images and print them to stdout.
175 users@, web page, Hacker News, Slashdot, Reddit