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.
51 Update OSNAME for mdocml:
53 vi contrib/mdocml/config.h
59 Edit \__DragonFly\_version and related comments. Put in commented numbers for the new release and master.
61 vi sys/conf/newvers.sh
63 Edit BRANCH, use 'DEVELOPMENT', update version.
65 vi gnu/usr.bin/groff/tmac/mdoc.local
67 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.
69 Update OSNAME for mdocml:
71 vi contrib/mdocml/config.h
84 Before you tag, make sure there aren't any last minute surprises - build this new branch, current version, whatever.
88 Make sure all changes on the master branch **and** on the new branch have been committed and pushed before tagging anything.
92 git add sys/sys/param.h sys/conf/newvers.sh gnu/usr.bin/groff/tmac/mdoc.local etc/Makefile.usr contrib/mdocml/config.h
98 git add sys/sys/param.h sys/conf/newvers.sh gnu/usr.bin/groff/tmac/mdoc.local contrib/mdocml/config.h
103 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.
105 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.
107 export GPG_TTY=$(tty)
116 git tag -s -m "DragonFly x.x.0" vx.x.0
121 git tag -s -m "DragonFly x.y.0rc" vx.y.0rc
124 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.
126 A new tag may require a commit beforehand to the release branch to make sure it goes to the right branch.
128 ## Subsequent tag updates
130 When updating a x.x.1 version, you just need to tag.
132 If there's a significant change between versions - major library change or third-party software update, which is more likely in the development branch of DragonFly - update param.h
138 Generally, any files not specifically mentioned above as specific to a branch should be updated in master and then cherry-picked to the release branch. src/UPDATING is the most common example.
143 Adjust the default pkg checkout in /usr/src/etc/Makefile.usr for both master and the new branch if necessary.
145 dports for the new release should be built before announcing, so that people testing the release, or a release candidate, can install with immediately available packages.
147 ### Build isos and imgs
149 Make sure there's an appropriate dports path for pkg to download from when building images - especially release candidates. When there is a major version change, the packages for master will not be named correctly. (i.e. going from 3.8 to 4.0 means that the master packages were in 3.10, and the directory arrangement will reflect that). Tag, get packages built, **then** create initial ISO/IMG files.
151 Set DPORTS_PATH when building the image to pick where dports comes from. Ideally, there should be a release tag in dports that corresponds with the DragonFly release.
156 If your ISO is too big for a normal CD, try stripping modules. Make sure to use a blank make.conf so local changes don't interfere. Here's the "final" string:
158 make -DINSTALLSTRIPPEDMODULES DPORTS_PATH=/the/path __MAKE_CONF=/dev/null release
160 To build it. (add pkg/gui/whatever targets as necessary.)
164 Testing should be done on real hardware, qemu and vmware. We have six isos/imgs that needs testing.
166 i386 iso, img, gui-img<br/>
167 x86_64 iso, img, gui-img
171 * Booting install media.
172 * Installing; encrypted, unencrypted, ufs, hammer.
173 * Configuring everything in the installer; try both dhcp and static IP.
174 * Booting the installed system.
178 Copy one of the existing release pages. The general format is :
180 * General announcement
181 * Big items new to this release
182 * Availability, describing what can be run
183 * MD5 results for compressed and uncompressed files
184 * Special notes and caveats
185 * Release notes - go through git log for these.
187 Complete, or at least mostly complete, before announcing any versions.
191 * Update the release page, the main page, and the general [[Download]] page.
192 * Add new MD5 sums on the release page for the compressed and uncompressed files.
196 Place images in /ftp/iso-images on crater.dragonflybsd.org. They will be rsynced to mirror-master.
198 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.
200 /root/adm/domd5.sh will get the MD5 sums for the compressed and uncompressed images and print them to stdout. The script will run faster if you edit it to only check the new files, and then manually add the lines to md5.txt.
202 A BitTorrent setup would be desirable, but there's no standard process for it as part of release, yet.
205 users@, web page, Hacker News, Slashdot, Reddit