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.

+Update OSNAME for mdocml:

+

+ vi contrib/mdocml/config.h

+

+

+## Safety check

+

+Before you tag, make sure there aren't any last minute surprises - build this new branch, current version, whatever.

+

##Tagging

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

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

-##Pkgsrc

+DragonFly-current looks to the next even number release, so until the path is created on mirror-master, ${ABI} will have to be set manually in /usr/local/etc/pkg/repos/df-latest.conf by any -current users.

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

+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.

-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 isos and imgs

+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.

+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.

+ git fetch --tags

+ git checkout TAGNAME

-###build pkgsrc packages

+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:

@@ -150,18+178,22 @@ Copy one of the existing release pages. The general format is :

* Special notes and caveats

* Release notes - go through git log for these.

+Complete, or at least mostly complete, before announcing any versions.

+

#### Minor releases

* Update the release page, the main page, and the general [[Download]] page.

* Add new MD5 sums on the release page for the compressed and uncompressed files.

-###File Copy

+###File Copy

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

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.

-/root/adm/domd5.sh will get the MD5 sums for the compressed and uncompressed images and print them to stdout.

+/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.

+

+A BitTorrent setup would be desirable, but there's no standard process for it as part of release, yet.