Diff for /wikisrc/releng/release-prep.mdwn between versions 1.8 and 1.9

version 1.8, 2014/01/21 01:40:55 version 1.9, 2014/04/12 18:47:26
Line 36  Cutting release candidates and releases: Line 36  Cutting release candidates and releases:
      distribution sets so they'll fit on floppies."       distribution sets so they'll fit on floppies."
    - Update Dd (should be the day the release is tagged)     - Update Dd (should be the day the release is tagged)
    - Update version numbers     - Update version numbers
    - Add mention of the latest CHANGES-<version> file in the "Release     - Add mention of the latest CHANGES-&lt;version&gt; file in the "Release
      Contents" section       Contents" section
    - List changes present in this release     - List changes present in this release
    - Adjust known issues section as necessary     - Adjust known issues section as necessary
Line 46  Cutting release candidates and releases: Line 46  Cutting release candidates and releases:
      section from the notes entirely).       section from the notes entirely).
   
    Note: the "changes" part of this should be taken from an mdoc file that     Note: the "changes" part of this should be taken from an mdoc file that
    is generated from <code>htdocs/releases/formal-<BLAH>/changes<VERSION>.xml</code>.     is generated from <code>htdocs/releases/formal-&lt;BLAH&gt;/changes&lt;VERSION&gt;.xml</code>.
    Look for ".Ss Changes Between the NetBSD" in distrib/notes/common/main     Look for ".Ss Changes Between the NetBSD" in distrib/notes/common/main
    and paste away!  You may have to make a few markup changes to the contents     and paste away!  You may have to make a few markup changes to the contents
    of the mdoc file, because the XML -> mdoc converter sucks.  Always check to     of the mdoc file, because the XML -> mdoc converter sucks.  Always check to
    make sure things are formatted as intended.     make sure things are formatted as intended.
   
    Basically, in htdocs/releases/formal-\<blah>, copy the previous release's     Basically, in htdocs/releases/formal-&lt;blah&gt;, copy the previous
    XML files, adjust Makefile as necessary, and start the dull process of     release's XML files, adjust Makefile as necessary, and start the dull
    adding content.  Beware that this is a soul-sucking task, and you MUST     process of adding content.  Beware that this is a soul-sucking task,
    RESIST THE TEMPTATION TO MENTION EVERY LITTLE CHANGE.  Try to keep it     and you MUST RESIST THE TEMPTATION TO MENTION EVERY LITTLE CHANGE.  Try
    to a list of things that people will be excited about and will sell     to keep it to a list of things that people will be excited about and
    NetBSD.  Release notes != changelog.     will sell NetBSD.  Release notes != changelog.
   
    Don't forget to edit <code>htdocs/layout.xml</code> and add an entry for the new page.     Don't forget to edit <code>htdocs/layout.xml</code> and add an entry for
      the new page.
   
 2. Update version numbers in <code>gnu/usr.bin/groff/tmac/mdoc.local</code> and  2. Update version numbers in <code>gnu/usr.bin/groff/tmac/mdoc.local</code> and
    sys/sys/param.h.  Add new CHANGES file to doc/README.files, updating     sys/sys/param.h.  Add new CHANGES file to doc/README.files, updating
    release numbers while there.  Make sure <code>doc/LAST_MINUTE</code> is zeroed out     release numbers while there.  Make sure <code>doc/LAST_MINUTE</code> is zeroed out
    and adjust version number.     and adjust version number.
   
 3. Note changes from step 2 in doc/CHANGES-\<whatever>  3. Note changes from steps 1 and 2 in doc/CHANGES-&lt;whatever&gt;
   
 4. <code>cvs -f rtag -a -rnetbsd-5 netbsd-5-0-RELEASE src xsrc</code>  4. <code>cvs -f rtag -a -rnetbsd-5 netbsd-5-0-RELEASE src xsrc</code>
   
    If something needs to be retagged after the fact:     If something needs to be retagged after the fact:
   
    - Change \<file> on the netbsd-5 branch.     - Change &lt;file&gt; on the netbsd-5 branch.
    - <code>cvs tag -d netbsd-5-0-RELEASE \<file></code>     - <code>cvs tag -d netbsd-5-0-RELEASE &lt;file&gt;</code>
    - <code>cvs tag -rnetbsd-5 netbsd-5-0-RELEASE \<file></code>     - <code>cvs tag -rnetbsd-5 netbsd-5-0-RELEASE &lt;file&gt;</code>
   
 5. Add tag (netbsd-5-0-RELEASE) to <code>~builds/etc/archlist</code> on build.netbsd.org  5. Add tag (netbsd-5-0-RELEASE) to <code>~builds/etc/archlist</code> on build.netbsd.org
    Add tag to <code>AB_STICKY_TAG_LIST</code> in <code>~builds/etc/autobuild.conf</code>.  Note that     Add tag to <code>AB_STICKY_TAG_LIST</code> in <code>~builds/etc/autobuild.conf</code>.  Note that
Line 97  Cutting release candidates and releases: Line 98  Cutting release candidates and releases:
    and proceed.     and proceed.
   
 8. Create ISOs (macppc, mac68k, source).  See below for instructions.  8. Create ISOs (macppc, mac68k, source).  See below for instructions.
    Rename ISOs to blahcd-\<release>.iso     Rename ISOs to blahcd-&lt;release&gt;.iso
    Create hashes for ISOs (<code>cksum -a 512 *iso > SHA512</code>)     Create hashes for ISOs (<code>cksum -a 512 *iso > SHA512</code>)
   
 9. rsync to nbftp.  It goes to a staging dir in /pub/NetBSD/misc/releng first.  9. rsync to nbftp.  It goes to a staging dir in /pub/NetBSD/misc/releng first.
   
         rsync -avu --progress --port 874 --password-file /home/builds/.rsync \<path-to-top-level-release-dir> builds@ftp.netbsd.org::builds/          rsync -avu --progress --port 874 --password-file /home/builds/.rsync &lt;path-to-top-level-release-dir&gt; builds@ftp.netbsd.org::builds/
 This will upload the files to <code>ftp.NetBSD.org:/pub/NetBSD/misc/releng/</code>.  This will upload the files to <code>ftp.NetBSD.org:/pub/NetBSD/misc/releng/</code>.
    After that, get admins to create <code>/pub/NetBSD/NetBSD-\<release></code> and     After that, get admins to create <code>/pub/NetBSD/NetBSD-&lt;release&gt;</code> and
    <code>/pub/NetBSD/iso/<release></code> directories for you, owned by builds:builds.     <code>/pub/NetBSD/iso/&lt;release&gt;</code> directories for you, owned by builds:builds.
    Once these have been made, move images/* to the iso directory and symlink to "iso" and "images" in the main release directory, and move the rest     Once these have been made, move images/* to the iso directory and symlink to "iso" and "images" in the main release directory, and move the rest
    to the main release directory.     to the main release directory.
   
Line 141  This will upload the files to <code>ftp. Line 142  This will upload the files to <code>ftp.
   
 15. Update the website.  15. Update the website.
   
     Commit release's HTML file in htdocs/releases/formal-&lt;blah&gt;
     Add htdocs/support/security/patches-&lt;blah&gt;
     Update htdocs/releases/formal-&lt;blah&gt;/index.xml
     Update htdocs/mirrors/torrents/
     Update htdocs/share/xml/misc.ent (release.*)
     Update htdocs/index.html
     Update htdocs/releases/formal.xml
     Update htdocs/changes/index.xml
     Top-level regen of everything
   
 16. Update <code>/pub/NetBSD/README</code> to mention the new release  16. Update <code>/pub/NetBSD/README</code> to mention the new release
   
 17. Announce the release on netbsd-announce@ and the blog.  17. Announce the release on netbsd-announce@ and the blog.

Removed from v.1.8  
changed lines
  Added in v.1.9


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb