Fix the updating an XEP section of the README

This commit is contained in:
Sam Whited 2016-05-16 15:14:58 -05:00
parent 285ab39134
commit a668b2a5e8
1 changed files with 19 additions and 1 deletions

View File

@ -22,6 +22,12 @@
<supersededby/>
<shortname>N/A</shortname>
&stpeter;
<revision>
<version>0.2</version>
<date>2016-05-16</date>
<initials>ssw</initials>
<remark><p>Make the updating an XEP section match current process.</p></remark>
</revision>
<revision>
<version>0.10</version>
<date>2016-01-21</date>
@ -145,9 +151,21 @@
<li>Verify that the version number, status, and other information are correct.</li>
<li>Compile the file locally and check the content for accuracy (including the correct date and version number).</li>
<li>Check the changes into source control.</li>
<li>Log into the webserver, change directories to /home/xsf/xmpp-hg/extensions, run the "archive.sh" script to copy the previous XEP version to the "attic" (just in case the last editor team member forgot), type 'hg pull' and 'hg update', and run the "gen.py" script to generate HTML and PDF files.</li>
<li>Log into the webserver as the 'xsf' user, change directories to /home/xsf/xmpp-hg/extensions, run the "archive.sh" script to copy the previous XEP version to the "attic" (just in case the last editor team member forgot), type 'hg pull' and 'hg update', and run the "gen.py" script to generate HTML and PDF files.</li>
<li>Run the "announce.py" script on the webserver (see note about <link url='#lists'>List Administration</link>).</li>
</ol>
<p>For example, to update XEP-0353 from version 0.1 to 0.2, you might do something like the following:</p>
<code><![CDATA[
$ sudo -u xsf -i
$ cd ~xsf/xmpp-hg/extensions
$ . /usr/local/virtualenv/gen/activate
$ # or "export PATH=/usr/local/virtualenv/gen/bin:$PATH
$ ./archive.sh 0353 0.1
$ hg pull && hg update
$ ./gen.py xep-0353.xml
$ ./announce.py 0353 http://xmpp.org/extensions/diff/api/xep/0353/diff/0.1/vs/0.2
]]></code>
</section2>
<section2 topic='Deferring a XEP' anchor='deferring'>