incubator-sling-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache Sling Website > Release Management
Date Tue, 26 Jan 2010 10:24:00 GMT
<html>
<head>
    <base href="http://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/1519/1/1/_/styles/combined.css?spaceKey=SLINGxSITE&amp;forWysiwyg=true"
type="text/css">
    </head>
<body style="background-color: white" bgcolor="white">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
     <h2><a href="http://cwiki.apache.org/confluence/display/SLINGxSITE/Release+Management">Release
Management</a></h2>
     <h4>Page <b>edited</b> by             <a href="http://cwiki.apache.org/confluence/display/~cziegeler@apache.org">Carsten
Ziegeler</a>
    </h4>
     
          <br/>
     <div class="notificationGreySide">
         <h1><a name="ReleaseManagement-ReleaseManagement"></a>Release Management</h1>


<p>Sling releases (and SNAPSHOTS) are deployed to the  <a href="http://repository.apache.org"
rel="nofollow">Nexus repository</a> instead of the traditional deployment via the
Maven 2 mirros source on <tt>people.apache.org</tt>. This makes the release process
much leaner and simpler. In addtion we can benefit from the Apache Parent POM 6, which has
most of the release profile setup built-in.</p>

<p>Most of the hard work of preparing and deploying the release is done by Maven.</p>

<div>
<ul>
    <li><a href='#ReleaseManagement-Prerequisites'>Prerequisites</a></li>
    <li><a href='#ReleaseManagement-StagingtheReleaseCandidates'>Staging the Release
Candidates</a></li>
    <li><a href='#ReleaseManagement-StartingtheVote'>Starting the Vote</a></li>
    <li><a href='#ReleaseManagement-WaitfortheResults'>Wait for the Results</a></li>
    <li><a href='#ReleaseManagement-CancelingtheRelease'>Canceling the Release</a></li>
    <li><a href='#ReleaseManagement-PromotingtheRelease'>Promoting the Release</a></li>
    <li><a href='#ReleaseManagement-UpdateJIRA'>Update JIRA</a></li>
    <li><a href='#ReleaseManagement-CreateanAnnouncement'>Create an Announcement</a></li>
    <li><a href='#ReleaseManagement-RelatedLinks'>Related Links</a></li>
    <li><a href='#ReleaseManagement-AppendixA%3ACreateandAddyourkeyto'>Appendix
A: Create and Add your key to http://www.apache.org/dist/sling/KEYS</a></li>
    <li><a href='#ReleaseManagement-AppendixB%3ApreparingreleasesonMacOSX'>Appendix
B: preparing releases on Mac OS X</a></li>
    <li><a href='#ReleaseManagement-AppendixC%3ADeploybundlesontheSlingOBR'>Appendix
C: Deploy bundles on the Sling OBR</a></li>
</ul></div>



<h2><a name="ReleaseManagement-Prerequisites"></a>Prerequisites</h2>

<ul>
	<li>To prepare or perform a release you <b>MUST BE</b> at least be an Apache
Sling Committer.</li>
	<li>Each and every release must be signed; therefore the public key should be cross
signed by other Apache committers (not required but suggested) and this public key should
be added to <a href="http://www.apache.org/dist/sling/KEYS" rel="nofollow">http://www.apache.org/dist/sling/KEYS</a>
(See Appendix A)</li>
	<li>When preparing the release on Mac OS X, check out Appendix B before trying the
steps in the next chapter.</li>
	<li>Make sure you have all Apache servers defined in your <a href="http://maven.apache.org/developers/committer-settings.html"
rel="nofollow">settings.xml</a></li>
</ul>


<p><b>Note</b>: Listing the Apache servers in the <tt>settings.xml</tt>
file also requires adding the password to that file. Starting with Maven 2.1 this password
may be encrypted and needs not be give in plaintext. Please refer to <a href="http://maven.apache.org/guides/mini/guide-encryption.html"
rel="nofollow">Password Encryption</a> for more information.</p>

<p>In the past we staged release candidates on our local machines using a semi-manual
process. Now that we inherit from the Apache parent POM version 6, a repository manager will
automatically handle staging for you. This means you now only need to specify your GPG passphrase
in the release profile of your <tt>${user.home}/.m2/settings.xml</tt>:</p>

<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-xml">
<span class="code-tag">&lt;settings&gt;</span>
    ...
    <span class="code-tag">&lt;profiles&gt;</span>
        <span class="code-tag">&lt;profile&gt;</span>
            <span class="code-tag">&lt;id&gt;</span>apache-release<span
class="code-tag">&lt;/id&gt;</span>
            <span class="code-tag">&lt;properties&gt;</span>
                <span class="code-tag">&lt;gpg.passphrase&gt;</span> <span
class="code-tag"><span class="code-comment">&lt;!-- YOUR KEY PASSPHRASE --&gt;</span></span>
<span class="code-tag">&lt;/gpg.passphrase&gt;</span>
            <span class="code-tag">&lt;/properties&gt;</span>
        <span class="code-tag">&lt;/profile&gt;</span>
    <span class="code-tag">&lt;/profiles&gt;</span>
    ...
<span class="code-tag">&lt;/settings&gt;</span>
</pre>
</div></div>

<p>Everything else has been configured in the latest Sling Parent POM:</p>

<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-xml">
<span class="code-tag">&lt;parent&gt;</span>
    <span class="code-tag">&lt;groupId&gt;</span>org.apache.sling<span
class="code-tag">&lt;/groupId&gt;</span>
    <span class="code-tag">&lt;artifactId&gt;</span>sling<span class="code-tag">&lt;/artifactId&gt;</span>
    <span class="code-tag">&lt;version&gt;</span>6<span class="code-tag">&lt;/version&gt;</span>
<span class="code-tag">&lt;/parent&gt;</span>
</pre>
</div></div>



<h2><a name="ReleaseManagement-StagingtheReleaseCandidates"></a>Staging
the Release Candidates</h2>

<p>First prepare your POMs for release:</p>

<ol>
	<li>Make sure there are no snapshots in the POMs to be released</li>
	<li>Check that your POMs will not lose content when they are rewritten during the release
process
<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
<pre>$ mvn release:prepare -DdryRun=true
</pre>
</div></div>
<p>Compare the original <tt>pom.xml</tt> with the one called <tt>pom.xml.tag</tt>
to see if the license or any other info has been removed. This has been known to happen if
the starting <tt>&lt;project&gt;</tt> tag is not on a single line. The
only things that should be different between these files are the <tt>&lt;version&gt;</tt>
and <tt>&lt;scm&gt;</tt> elements. If there are any other changes, you
must fix the original <tt>pom.xml</tt> file and commit before proceeding with
the release.</p></li>
	<li>Publish a snapshot
<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
<pre>$ mvn deploy
...
[INFO] [deploy:deploy]
[INFO] Retrieving previous build number from apache.snapshots.https
...
</pre>
</div></div>
	<ul>
		<li>If you experience an error during deployment like a HTTP 401 check your settings
for the required server entries as outlined in the <b>Prerequisites</b></li>
		<li>Be sure that the generated artifacts respect the Apache release <a href="http://www.apache.org/dev/release.html"
rel="nofollow">rules</a>: NOTICE and LICENSE files should be present in the META-INF
directory within the jar. For -sources artifacts, be sure that your POM does not use the maven-source-plugin:2.0.3
which is broken. The recommended version at this time is 2.0.4</li>
		<li>You should verify the deployment under the <a href="https://repository.apache.org/content/groups/snapshots/org/apache/sling"
rel="nofollow">snapshot</a> repository on Apache</li>
	</ul>
	</li>
	<li>Prepare the release
<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
<pre>$ mvn release:clean
$ mvn release:prepare
</pre>
</div></div>
	<ul>
		<li>Preparing the release will create the new tag in SVN, automatically checking in
on your behalf</li>
		<li>If you get a build failure because of an SVN commit problem (namely <em>The
specified baseline is not the latest baseline, so it may not be checked out.</em>),
just repeat the <tt>mvn release:prepare</tt> command until SVN is happy. This
is based on a known timing issue when using the European SVN mirror.</li>
	</ul>
	</li>
	<li>Stage the release for a vote
<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
<pre>$ mvn release:perform
</pre>
</div></div>
	<ul>
		<li>The release will automatically be inserted into a temporary staging repository
for you, see the Nexus <a href="http://www.sonatype.com/books/nexus-book/reference/staging.html"
rel="nofollow">staging documentation</a> for full details</li>
		<li>You can continue to use <tt>mvn release:prepare</tt> and <tt>mvn
release:perform</tt> on other sub-projects as necessary on the same machine and they
will be combined in the same staging repository - this is useful when making a release of
multiple Sling modules.</li>
	</ul>
	</li>
	<li>Close the staging repository
	<ul>
		<li>Login to <a href="https://repository.apache.org" rel="nofollow">https://repository.apache.org</a>
using your Apache SVN credentials. Click on <b>Staging</b> on the left. Then click
on <b>org.apache.sling</b> in the list of repositories. In the panel below you
should see an open repository that is linked to your username and IP. Right click on this
repository and select <b>Close</b>. This will close the repository from future
deployments and make it available for others to view. If you are staging multiple releases
together, skip this step until you have staged everything</li>
	</ul>
	</li>
	<li>Verify the staged artifacts
	<ul>
		<li>If you click on your repository, a tree view will appear below. You can then browse
the contents to ensure the artifacts are as you expect them. Pay particular attention to the
existence of &#42;.asc (signature) files. If you don't like the content of the repository,
right click your repository and choose <b>Drop</b>. You can then rollback your
release (see <b>Canceling the Release</b>) and repeat the process</li>
		<li>Note the staging repository URL (especially the number at the end of the URL)
you will need this in your vote email</li>
	</ul>
	</li>
</ol>




<h2><a name="ReleaseManagement-StartingtheVote"></a>Starting the Vote</h2>

<p>Propose a vote on the dev list with the closed issues, the issues left, and the staging
repository - for example:</p>

<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
<pre>To: "Sling Developers List" &lt;dev@sling.apache.org&gt;
Subject: [VOTE] Release Apache Sling ABC version X.Y.Z

Hi,

We solved N issues in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/...

There are still some outstanding issues:
https://issues.apache.org/jira/browse/SLING/component/...

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-[YOUR REPOSITORY ID]/

You can use this UNIX script to download the release and verify the signatures:
http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh [YOUR REPOSITORY ID] /tmp/sling-staging

Please vote to approve this release:

  [ ] +1 Approve the release
  [ ]  0 Don't care
  [ ] -1 Don't release, because ...

This vote will be open for 72 hours.
</pre>
</div></div>



<h2><a name="ReleaseManagement-WaitfortheResults"></a>Wait for the Results</h2>

<p>From <a href="http://www.apache.org/foundation/voting.html" rel="nofollow">Votes
on Package Releases</a>:</p>

<blockquote><p>Votes on whether a package is ready to be released follow a format
similar to majority approval &#8211; except that the decision is officially determined
solely by whether at least three +1 votes were registered. Releases may not be vetoed. Generally
the community will table the vote to release if anyone identifies serious problems, but in
most cases the ultimate decision, once three or more positive votes have been garnered, lies
with the individual serving as release manager. The specifics of the process may vary from
project to project, but the 'minimum of three +1 votes' rule is universal.</p></blockquote>


<p>The list of binding voters is available on the <a href="/confluence/display/SLINGxSITE/Project+Team"
title="Project Team">Project Team</a> page.</p>


<p>If the vote is successful, post the result to the dev list - for example:</p>


<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
<pre>To: "Sling Developers List" &lt;dev@sling.apache.org&gt;
Subject: [RESULT] [VOTE] Release Apache Sling ABC version X.Y.Z

Hi,

The vote has passed with the following result :

+1 (binding): &lt;&lt;list of names&gt;&gt;
+1 (non binding): &lt;&lt;list of names&gt;&gt;

I will copy this release to the Felix dist directory and
promote the artifacts to the central Maven repository.
</pre>
</div></div>

<p>Be sure to include all votes in the list and indicate which votes were binding. Consider
-1 votes very carefully. While there is technically no veto on release votes, there may be
reasons for people to vote -1. So sometimes it may be better to cancel a release when someone,
especially a member of the PMC, votes -1.</p>

<p>If the vote is unsuccessful, you need to fix the issues and restart the process -
see <b>Canceling the Release</b>.</p>

<p>If the vote is successful, you need to promote and distribute the release - see <b>Promoting
the Release</b>.</p>



<h2><a name="ReleaseManagement-CancelingtheRelease"></a>Canceling the Release</h2>

<p>If the vote fails, or you decide to redo the release:</p>

<ol>
	<li>Remove the release tag from Subversion (<tt>svn del ...</tt>)</li>
	<li>Login to <a href="https://repository.apache.org" rel="nofollow">https://repository.apache.org</a>
using your Apache SVN credentials. Click on <b>Staging</b> on the left. Then click
on <b>org.apache.sling</b> in the list of repositories. In the panel below you
should see a closed repository that is linked to your username and IP (if it's not yet closed
you need to right click and select <b>Close</b>). Right click on this repository
and select <b>Drop</b>.</li>
	<li>Rollback the version in the <tt>pom.xml</tt> and commit any fixes you
need to make</li>
</ol>




<h2><a name="ReleaseManagement-PromotingtheRelease"></a>Promoting the Release</h2>

<p>If the vote passes:</p>

<ol>
	<li>Copy the released artifacts to the Sling dist directory (<tt>/x1/www/www.apache.org/dist/sling</tt>)
on <tt>people.apache.org</tt></li>
	<li>Delete the old release from the Sling dist directory (it's archived)</li>
	<li>Login to <a href="https://repository.apache.org" rel="nofollow">https://repository.apache.org</a>
with your Apache SVN credentials. Click on <b>Staging</b>. Find your closed staging
repository, right click on it and choose <b>Promote</b>. Select the <b>Releases</b>
repository from the drop-down list and click <b>Promote</b>.</li>
	<li>Next click on <b>Repositories</b>, select the <b>Releases</b>
repository and validate that your artifacts are all there</li>
	<li>If you're releasing bundles, you should also add them to the Sling Release OBR
(see <b>Appendix C</b>).</li>
	<li>Update the news section on the website at <a href="/confluence/display/SLINGxSITE/News"
title="News">News</a></li>
	<li>Update the download page on the website at <a href="/confluence/display/SLINGxSITE/Downloads"
title="Downloads">Downloads</a> to point to the new release.</li>
</ol>


<p>For the last two tasks, it's better to give the mirrors some time to distribute the
uploaded artifacts (one day should be fine). This ensures that once the website (news and
download page) is updated, people can actually download the artifacts.</p>



<h2><a name="ReleaseManagement-UpdateJIRA"></a>Update JIRA</h2>

<p>Go to <a href="https://issues.apache.org/jira/secure/project/ManageVersions.jspa?pid=12310710"
rel="nofollow">Manage Versions</a> section on the SLING JIRA and mark the X.Y.Z version
as released setting the release date to the date the vote has been closed.</p>

<p>Also create a new version X.Y.Z+2, if that hasn't already been done.</p>



<h2><a name="ReleaseManagement-CreateanAnnouncement"></a>Create an Announcement</h2>

<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
<pre>To: "Sling Developers List" &lt;dev@sling.apache.org&gt;, "Apache Announcements"
&lt;announce@apache.org&gt;
Subject: [ANN] Apache Sling ABC version X.Y.Z Released

The Apache Sling team is pleased to announce the release of Apache Sling ABC version X.Y.Z

&lt;&lt;insert short description of the sub-project&gt;&gt;

http://sling.apache.org/site/apache-felix-ABC.html

This release is available from http://sling.apache.org/site/downloads.cgi and Maven:

&lt;dependency&gt;
    &lt;groupId&gt;org.apache.sling&lt;/groupId&gt;
    &lt;artifactId&gt;org.apache.sling.ABC&lt;/artifactId&gt;
    &lt;version&gt;X.Y.Z&lt;/version&gt;
&lt;/dependency&gt;


Release Notes:

&lt;&lt;insert release notes in text format from JIRA&gt;&gt;

Enjoy!

-The Sling team
</pre>
</div></div>


<p><b>Important</b>: Add the release to the Software section of the next
board report below <a href="/confluence/display/SLING/Reports" title="Reports">Reports</a>.</p>



<h2><a name="ReleaseManagement-RelatedLinks"></a>Related Links</h2>
<ol>
	<li><a href="http://www.apache.org/dev/release-signing.html" rel="nofollow">http://www.apache.org/dev/release-signing.html</a></li>
	<li><a href="http://wiki.apache.org/incubator/SigningReleases" rel="nofollow">http://wiki.apache.org/incubator/SigningReleases</a></li>
</ol>




<h2><a name="ReleaseManagement-AppendixA%3ACreateandAddyourkeyto"></a>Appendix
A: Create and Add your key to <a href="http://www.apache.org/dist/sling/KEYS" rel="nofollow">http://www.apache.org/dist/sling/KEYS</a></h2>

<p>Considering that you are using a *nix system with a working OpenSSH, GnuPG, and bash
you can create and add your own key with the following command:</p>

<ol>
	<li><em>Create a public/private pair key</em>:
<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
<pre>$ gpg --gen-key
</pre>
</div></div>
<p>When gpg asks for e-mail linked the key you  <b>MUST USE</b> the &lt;committer&gt;@apache.org
one<br/>
When gpg asks for comment linked the key you <em>SHOULD USE</em> "CODE SIGNING
KEY"</p></li>
	<li><em>Add the key to</em> <a href="http://www.apache.org/dist/sling/KEYS:"
rel="nofollow">http://www.apache.org/dist/sling/KEYS:</a> type the following command
replacing the word e-mail with your Apache's one (&lt;committer&gt;@apache.org).
<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
<pre>$ (gpg --list-sigs e-mail &amp;&amp; gpg --export --armor e-mail) &gt;
toadd.key
$ scp toadd.key people.apache.org:
$ ssh people.apache.org "cat toadd.key &gt;&gt; /x1/www/www.apache.org/dist/sling/KEYS"
</pre>
</div></div></li>
	<li>You are <b>DONE</b>, but to see the changes on <a href="http://www.apache.org/dist/sling/KEYS"
rel="nofollow">http://www.apache.org/dist/sling/KEYS</a> you must wait 2 hours</li>
</ol>




<h2><a name="ReleaseManagement-AppendixB%3ApreparingreleasesonMacOSX"></a>Appendix
B: preparing releases on Mac OS X</h2>

<p>When running the <tt>mvn release:prepare</tt> command on Mac OS X, you
might see the following error:</p>

<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-java">[INFO] Executing: svn --non-interactive commit --file /tmp/maven-scm-802409492.commit
--targets /tmp/maven-scm-18804-targets
[INFO] Working directory: /homedir/dev/felix/dependencymanager
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
svn: Commit failed (details follow):
svn: MKACTIVITY of '/repos/asf/!svn/act/4f11ad5d-9161-0410-b4dd-cb727141ea8c': authorization
failed (https:<span class="code-comment">//svn.apache.org)</span></pre>
</div></div>

<p>This is due to a bug in Subversion on the Mac, as described by Brett Porter in his
<a href="http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-subversion/"
rel="nofollow">blog</a>. He proposes putting an "svn" script at the head of your
path to fix the issue.</p>



<h2><a name="ReleaseManagement-AppendixC%3ADeploybundlesontheSlingOBR"></a>Appendix
C: Deploy bundles on the Sling OBR</h2>

<p>We are mainting an OSGi Bundle Repository providing all release of the Sling Bundles.
This repository is maintained as part of the Apache Sling site and is available at <a href="http://sling.apache.org/obr/sling.xml"
rel="nofollow">http://sling.apache.org/obr/sling.xml</a>. The source for this page
is maintained in the SVN repository below the <em>site</em>, that is at <a
href="http://svn.apache.org/repos/asf/sling/site/" rel="nofollow">http://svn.apache.org/repos/asf/sling/site/</a>.
To update the Sling OBR repository you must be an Apache Sling Committer since this requires
SVN write access.</p>

<p>To update the OBR you may use the Apache Felix Maven Bundle Plugin which prepares
the bundle descriptor to be added to the OBR file. Follow these steps to update the OBR:</p>

<p><b>1. Checkout or update the Site Source</b></p>

<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-java">
$ svn checkout https:<span class="code-comment">//svn.apache.org/repos/asf/sling/site</span>
</pre>
</div></div>

<p>Note, that you have to checkout the site using the <tt>https</tt> URL,
otherwise you will not be able to commit the changes later.</p>

<p><b>2. Deploy the Descriptor</b></p>

<p>To deploy the project descriptor, checkout the tag of the bundle to deploy and run
maven</p>

<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-java">
$ svn checkout http:<span class="code-comment">//svn.apache.org/repos/asf/sling/tags/the_module_tag
</span>$ mvn clean install \
    org.apache.felix:maven-bundle-plugin:deploy \
    -DprefixUrl=http:<span class="code-comment">//repo1.maven.org/maven2 \
</span>    -DremoteOBR=sling.xml \
    -DaltDeploymentRepository=apache.releases::<span class="code-keyword">default</span>::file:<span
class="code-comment">///path_to_site_checkout/obr</span>
</pre>
</div></div>

<p>This generates the bundle descriptor and adds it to the <tt>sling.xml</tt>
file of your site checkout.</p>


<p><b>2a. Variant: Refer to Maven Repository</b></p>

<p>Instead of checking out and building the project locally, you may also use the <tt>deploy-file</tt>
goal of the Maven Bundle Plugin:</p>

<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-java">
$ wget http:<span class="code-comment">//repo1.maven.org/maven2/org/apache/sling/the_module/version/the_module-version.jar
</span>$ wget http:<span class="code-comment">//repo1.maven.org/maven2/org/apache/sling/the_module/version/the_module-version.pom
</span>$ mvn org.apache.felix:maven-bundle-plugin:deploy-file \
    -Dfile=the_module-version.jar -DpomFile=the_module-version.pom \
    -DbundleUrl=http:<span class="code-comment">//repo1.maven.org/maven2/org/apache/sling/the_module/version/the_module-version.jar
\
</span>    -Durl=file:<span class="code-comment">///path_to_site_checkout/obr
\ 
</span>    -DprefixUrl=http:<span class="code-comment">//repo1.maven.org/maven2
\
</span>    -DremoteOBR=sling.xml
$ rm the_module-version.jar the_module-version.pom
</pre>
</div></div>


<p><b>3. Commite the Site Changes</b></p>

<p>In the Site checkout folder commit the changes to the <tt>obr/sling.xml</tt>
files (you may also review the changes using the <tt>svn diff</tt> command).</p>

<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-java">
$ svn commit -m<span class="code-quote">"Add Bundle ABC Version X.Y.Z"</span>
obr/sling.xml
</pre>
</div></div>


<p><b>4. Update the Site on <tt>people.apache.org</tt></b></p>

<p>After committing the changes, you have to update the site source, which is getting
mirrored to the web servers on <tt>people.apache.org</tt></p>

<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-java">
$ ssh people.apache.org svn update /x1/www/sling.apache.org/obr/sling.xml
</pre>
</div></div>

<p>After updating the site source it will generally take an hour or two until the changes
are visible on the web.</p>
     </div>
     <div id="commentsSection" class="wiki-content pageSection">
       <div style="float: right;">
            <a href="http://cwiki.apache.org/confluence/users/viewnotifications.action"
class="grey">Change Notification Preferences</a>
       </div>

       <a href="http://cwiki.apache.org/confluence/display/SLINGxSITE/Release+Management">View
Online</a>
       |
       <a href="http://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=117895&revisedVersion=14&originalVersion=13">View
Change</a>
              |
       <a href="http://cwiki.apache.org/confluence/display/SLINGxSITE/Release+Management?showComments=true&amp;showCommentArea=true#addcomment">Add
Comment</a>
            </div>
</div>
</div>
</div>
</div>
</body>
</html>

Mime
View raw message