Update Manifest: Difference between revisions
From MediaWiki
Jump to navigationJump to search
(New page: = Create the Release Manifest = You should create the file: "''include/manifest/release-${VERSION}.xml''" (if it does not yet exist). Initially, this should be a copy of the file: "''incl...) |
No edit summary |
||
(13 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
= Create the Release Manifest = | = Create the Release Manifest = | ||
You should create the file: "''include/manifest/release-${VERSION}.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''". | ||
[ | [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 = | = 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> | |||
Here is a template of the entities you are likely to need to add | * 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: | ||
<file id=" | <files> | ||
<name>nst- | <file id="iso64"> | ||
<label> | <name>nst-24-7977.x86_64.iso</name> | ||
<md5> | <label>ISO (64 bit)</label> | ||
<md5>10d018e4ac115eaf390554d8329bd4d4</md5> | |||
</file> | </file> | ||
<file id=" | <file id="tar.gz"> | ||
<name>nst- | <name>nst-24.tar.gz</name> | ||
<label> | <label>Source</label> | ||
<md5> | <md5>c2b076dac54fb345ea3f57cc403e8501</md5> | ||
</file> | </file> | ||
</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 18: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.