Difference between revisions of "Update Manifest"

From NST Wiki
Jump to navigationJump to search
(Edit File Information)
 
(7 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
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''".
 
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
+
  [nst@nst24-repo repo]$ cd include/manifest
  [root@nst-dev-32 manifest]# cp current.xml release-2.13.0-1715.xml
+
  [nst@nst24-repo repo]$ cp current.xml release-18-4509.xml
  [root@nst-dev-32 manifest]# svn add release-2.13.0-1715.xml
+
  [nst@nst24-repo repo]$ svn add release-18-4509.xml
 +
 
 +
NOTE: This should have been done earlier in the release process (if you had to do it now, then you skipped a step).
  
 
= Edit File Information =
 
= Edit File Information =
  
 
* At the start of the manifest file, you will need to change the ''released'' attribute to ''true''.
 
* 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:
 
* Make sure that the version and '''SVN''' revision are set correctly in the top information section:
  
 
   <name>nst</name>
 
   <name>nst</name>
   <version>2.16.0-3170</version>
+
   <version>24</version>
   <date>Mon Feb 27 13:47:55 EST 2012</date>
+
   <date>Sun Jul  3 15:24:51 EDT 2016</date>
 
   <passwordofs>tbd</passwordofs>
 
   <passwordofs>tbd</passwordofs>
 
   <svn>
 
   <svn>
     <root>https://nst.svn.sourceforge.net/svnroot/nst</root>
+
     <root>https://svn.code.sf.net/p/nst/code/repo</root>
     <branch>trunk</branch>
+
     <branch>24</branch>
     <revision>3170</revision>
+
     <revision>7977</revision>
 
   </svn>
 
   </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":
+
* 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/update:
  
 
   <files>
 
   <files>
     <file id="iso">
+
     <file id="iso64">
       <name>nst-2.16.0-3170.i686.iso</name>
+
       <name>nst-24-7977.x86_64.iso</name>
       <label>ISO (32 bit)</label>
+
       <label>ISO (64 bit)</label>
       <md5>21afa19900448c7dfc2466ddde670e69</md5>
+
       <md5>10d018e4ac115eaf390554d8329bd4d4</md5>
 
     </file>
 
     </file>
 
   
 
   
 
     <file id="tar.gz">
 
     <file id="tar.gz">
       <name>nst-2.16.0-3170.tar.gz</name>
+
       <name>nst-24.tar.gz</name>
 
       <label>Source</label>
 
       <label>Source</label>
       <md5>a7172d9620ab42c720a33e55bec8b2aa</md5>
+
       <md5>c2b076dac54fb345ea3f57cc403e8501</md5>
 
     </file>
 
     </file>
  </files>
+
</files>
 
  
 
Note: The MD5 values will need to be updated for your release!
 
Note: The MD5 values will need to be updated for your release!

Latest revision as of 19:37, 3 July 2016

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

[nst@nst24-repo repo]$ cd include/manifest
[nst@nst24-repo repo]$ cp current.xml release-18-4509.xml
[nst@nst24-repo repo]$ svn add release-18-4509.xml

NOTE: This should have been done earlier in the release process (if you had to do it now, then you skipped a step).

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>24</version>
 <date>Sun Jul  3 15:24:51 EDT 2016</date>
 <passwordofs>tbd</passwordofs>
 <svn>
   <root>https://svn.code.sf.net/p/nst/code/repo</root>
   <branch>24</branch>
   <revision>7977</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/update:
 <files>
   <file id="iso64">
     <name>nst-24-7977.x86_64.iso</name>
     <label>ISO (64 bit)</label>
     <md5>10d018e4ac115eaf390554d8329bd4d4</md5>
   </file>

   <file id="tar.gz">
     <name>nst-24.tar.gz</name>
     <label>Source</label>
     <md5>c2b076dac54fb345ea3f57cc403e8501</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.