directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r873497 - in /websites/staging/directory/trunk/content: ./ mavibot/developer-guide.html
Date Thu, 08 Aug 2013 13:40:49 GMT
Author: buildbot
Date: Thu Aug  8 13:40:48 2013
New Revision: 873497

Staging update by buildbot for directory

    websites/staging/directory/trunk/content/   (props changed)

Propchange: websites/staging/directory/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Thu Aug  8 13:40:48 2013
@@ -1 +1 @@

Modified: websites/staging/directory/trunk/content/mavibot/developer-guide.html
--- websites/staging/directory/trunk/content/mavibot/developer-guide.html (original)
+++ websites/staging/directory/trunk/content/mavibot/developer-guide.html Thu Aug  8 13:40:48
@@ -362,71 +362,107 @@ Emmanuel
 <h2 id="release">Release</h2>
 <p>If the vote succeeds the Mavibot project can be released.</p>
-<p>Go to and release the
staging repository so all artifacts are published to Maven central.</p>
-<p>Move the distribution packages (sources and binaries) to the dist SVN repository:$(version)</p>
+<p>Go to <a href=""></a>
and release the staging repository so all artifacts are published to Maven central.</p>
+<p>Move the distribution packages (sources and binaries) to the dist SVN repository:
+<div class="codehilite"><pre><span class="o">**</span><span class="n">https</span><span
class="p">:</span><span class="o">//</span><span class="n">dist</span><span
class="p">.</span><span class="n">apache</span><span class="p">.</span><span
class="n">org</span><span class="o">/</span><span class="n">repos</span><span
class="o">/</span><span class="n">dist</span><span class="o">/</span><span
class="n">release</span><span class="o">/</span><span class="n">directory</span><span
class="o">/</span><span class="n">mavibot</span><span class="o">/</span><span
class="n">dist</span><span class="o">/</span>$<span class="p">(</span><span
class="n">version</span><span class="p">)</span><span class="o">**</span>
 <p>The best solution would be to checkout the directory in, to copy
the packages in the right place, and to check in the changes :</p>
-<p>$ ssh</p>
-<h1 id="svn-co-httpsdistapacheorgreposdistreleasedirectorymavibotdist-api-dist">svn
co api-dist</h1>
-<h1 id="cd-api-dist">cd api-dist</h1>
-<h1 id="mkdir-wzxhzdk22">mkdir <version></h1>
-<h1 id="cp-public_htmlmavibot-wzxhzdk23-wzxhzdk24">cp ../public_html/mavibot-<version>/*
-<h1 id="svn-ci-wzxhzdk25">svn ci <version></h1>
-<h1 id="exit">exit</h1>
-<p>The packages should now be available on<version></p>
+<div class="codehilite"><pre>$ ssh
+# svn co api-dist
+# cd api-dist
+# mkdir &lt;version&gt;
+# cp ../public_html/mavibot-&lt;version&gt;/* &lt;version&gt;
+# svn ci &lt;version&gt;
+# exit
+<p>The packages should now be available on <strong><version></strong></p>
 <h2 id="deploy-the-javadocs-and-xref">Deploy the Javadocs and XRef</h2>
 <p>We now can deploy the generated Javadoc and cross-reference pages. They are generated
in the following directory :</p>
+<div class="codehilite"><pre>target/checkout/target/site
 <p>We will copy two directories :</p>
-<div class="codehilite"><pre><span class="n">apidocs</span>
-<span class="n">xref</span>
+<div class="codehilite"><pre>apidocs
 <h3 id="staging-or-production">Staging or Production?</h3>
 <p>Those files will be stored on the production server only !!! And some extra caution
must be taken not to delete them when we will publish the staging site too...</p>
 <p>First of all, you must checkout the two CMS store for the site : staging and revision.</p>
-<p>$ cd ~/apacheds
+<div class="codehilite"><pre>$ cd ~/apacheds
 $ svn co staging
 $ svn co production
- ...</p>
+ ...
 <p>Now, you will first add the directory for the newly generated version :</p>
-<p>$ cd ~/apacheds/production/content/mavibot/gen-docs
-$ mkdir <version>
-$ svn add <version></p>
+<div class="codehilite"><pre>$ cd ~/apacheds/production/content/mavibot/gen-docs
+$ mkdir &lt;version&gt;
+$ svn add &lt;version&gt;
 <p>Then copy the generated docs :</p>
-<p>$ cp -r ~/apacheds/trunks/mavibot/target/checkout/target/site/apidocs ~/apacheds/production/content/mavibot/gen-docs/<version>
-$ cp -r ~/apacheds/trunks/mavibot/target/checkout/target/site/xref ~/apacheds/production/content/mavibot/gen-docs/<version>
-$ </p>
+<div class="codehilite"><pre>$ cp -r ~/apacheds/trunks/mavibot/target/checkout/target/site/apidocs
+$ cp -r ~/apacheds/trunks/mavibot/target/checkout/target/site/xref ~/apacheds/production/content/mavibot/gen-docs/&lt;version&gt;
 <p>You have to check in those directories :</p>
-<p>$ svn add <version>/*
-$ svn ci <version> -m "Injected <version> javadocs"</p>
-<p>Now, you have to update the staging site :
+<div class="codehilite"><pre>$ svn add &lt;version&gt;/*
+$ svn ci &lt;version&gt; -m &quot;Injected &lt;version&gt; javadocs&quot;
+<p>Now, you have to update the staging site :</p>
+<div class="codehilite"><pre>extpaths.txt
 <p>This file list the file on the production site that will not be overriden by the
publication of the staging site. It has to be updated</p>
-<p>$ cd ~/apacheds/staging/content/
-$ vi extpaths.txt</p>
+<div class="codehilite"><pre>$ cd ~/apacheds/staging/content/
+$ vi extpaths.txt
 <p>Add the following line :</p>
-<h1 id="mavibot">Mavibot</h1>
-<p>then save and check in the file
+<div class="codehilite"><pre>...
+# Mavibot
+<p>then save and check in the file <strong>.htaccess</strong></p>
 <p>We also have to update this file :</p>
-<p>$ cd ~/apacheds/staging/content/mavibot/gen-docs
-$ vi .htaccess</p>
+<div class="codehilite"><pre>$ cd ~/apacheds/staging/content/mavibot/gen-docs
+$ vi .htaccess
 <p>And update the two last lines to refer to the version you've just released :</p>
-<p>RewriteRule ^latest$ <version>/
-RewriteRule ^latest/(.*)$ <version>/$1</p>
+<div class="codehilite"><pre>RewriteRule ^latest$ &lt;version&gt;/
+RewriteRule ^latest/(.*)$ &lt;version&gt;/$1
 <p>Save and commit the file.</p>
 <h2 id="update-the-web-site">Update the web site</h2>
 <p>You can now update the site, add a news on the front page, and publish the site.</p>
 <h2 id="inform-the-world">Inform the world !</h2>
 <p>After 24h, you can now inform the world about the release.</p>
-<p>Send a mail to the users and dev mailing list, and one to the</p>
+<p>Send a mail to the users and dev mailing list, and one to the
 <p>You are done !</p>

View raw message