Update Manifest

Create the Release Manifest

You should create the file: "include/manifest/release-${VERSION}-${SVNREVISION}.xml" (if it does not yet exist). Initially, this should be a copy of the file: "include/manifest/current.xml".

[root@nst-dev-32 repo]# cd include/manifest
[root@nst-dev-32 manifest]# cp current.xml release-2.13.0-1715.xml
[root@nst-dev-32 manifest]# svn add release-2.13.0-1715.xml

Edit File Information

• At the start of the manifest file, you will need to change the released attribute to true.

 <release released="true">

• Make sure that the version and SVN revision are set correctly in the top information section:

 <name>nst</name>
 <version>2.16.0-3170</version>
 <date>Mon Feb 27 13:47:55 EST 2012</date>
 <passwordofs>tbd</passwordofs>
 <svn>
   <root>https://nst.svn.sourceforge.net/svnroot/nst</root>
   <branch>trunk</branch>
   <revision>3170</revision>
 </svn>

• In addition, you should check the "<files>" entities to make sure that the MD5 values are set correctly for the files you published. Here is a template of the entities you are likely to need to add to: "include/manifest/release-2.16.0-3170.xml":

 <files>
   <file id="iso">
     <name>nst-2.16.0-3170.i686.iso</name>
     <label>ISO (32 bit)</label>
     <md5>21afa19900448c7dfc2466ddde670e69</md5>
   </file>

   <file id="tar.gz">
     <name>nst-2.16.0-3170.tar.gz</name>
     <label>Source</label>
     <md5>a7172d9620ab42c720a33e55bec8b2aa</md5>
   </file>
 </files>

Note: The MD5 values will need to be updated for your release!

Commit The Updates

Don't forget to commit your changes after modifying or creating the release XML file.