You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by bu...@apache.org on 2014/10/11 23:31:11 UTC
svn commit: r925430 - in /websites/staging/sling/trunk/content: ./
documentation/development/release-management.html
Author: buildbot
Date: Sat Oct 11 21:31:11 2014
New Revision: 925430
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/development/release-management.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Oct 11 21:31:11 2014
@@ -1 +1 @@
-1630759
+1631127
Modified: websites/staging/sling/trunk/content/documentation/development/release-management.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/development/release-management.html (original)
+++ websites/staging/sling/trunk/content/documentation/development/release-management.html Sat Oct 11 21:31:11 2014
@@ -103,9 +103,11 @@
<li><a href="#update-jira">Update JIRA</a></li>
<li><a href="#create-an-announcement">Create an Announcement</a></li>
<li><a href="#related-links">Related Links</a></li>
+<li><a href="#releasing-the-sling-ide-tooling">Releasing the Sling IDE Tooling</a></li>
<li><a href="#appendix-a-create-and-add-your-key-to-httpspeopleapacheorgkeysgroupslingasc">Appendix A: Create and Add your key to https://people.apache.org/keys/group/sling.asc</a></li>
<li><a href="#appendix-b-maven-and-scm-credentials">Appendix B: Maven and SCM credentials</a></li>
<li><a href="#appendix-c-deploy-bundles-on-the-sling-obr">Appendix C: Deploy bundles on the Sling OBR</a></li>
+<li><a href="#appendix-d-releasing-the-sling-ide-tooling">Appendix D: Releasing the Sling IDE Tooling</a></li>
</ul>
</div>
<h2 id="prerequisites">Prerequisites</h2>
@@ -331,6 +333,65 @@ Enjoy!
<li><a href="http://www.apache.org/dev/release-signing.html">http://www.apache.org/dev/release-signing.html</a></li>
<li><a href="http://wiki.apache.org/incubator/SigningReleases">http://wiki.apache.org/incubator/SigningReleases</a></li>
</ol>
+<h2 id="releasing-the-sling-ide-tooling">Releasing the Sling IDE Tooling</h2>
+<p>While the Sling IDE tooling is built using Maven, the toolchain that it is based around does not cooperate well with the maven-release-plugin. As such, the release preparation and execution are slightly different. The whole process is outlined below, assuming that we start with a development version of 1.0.1-SNAPSHOT.</p>
+<ol>
+<li>set the fix version as released: <code>mvn tycho-versions:set-version -DnewVersion=1.0.2</code></li>
+<li>update the version of the source-bundle project to 1.0.2</li>
+<li>commit the change to svn </li>
+<li>manually tag in svn using <code>svn copy https://svn.apache.org/repos/asf/sling/trunk/tooling/ide https://svn.apache.org/repos/asf/sling/tags/sling-ide-tooling-1.0.2</code></li>
+<li>Checkout the version from the tag and proceed with the build from there <code>https://svn.apache.org/repos/asf/sling/tags/sling-ide-tooling-1.0.2</code></li>
+<li>build the project with p2/gpg signing enabled: <code>mvn clean package -Psign</code> </li>
+<li>build the source bundle from the source-bundle directory: <code>mvn clean package</code> </li>
+<li>copy the following artifacts to https://dist.apache.org/repos/dist/dev/sling/ide-tooling-1.0.2 <ol>
+<li>source bundle ( org.apache.sling.ide.source-bundle-1.0.2.zip )</li>
+<li>zipped p2 repository ( org.apache.sling.ide.p2update-1.0.2.zip ) </li>
+</ol>
+</li>
+<li>ensure the artifacts are checksummed and gpg-signed</li>
+<li>call the vote </li>
+<li>Update to next version: <code>mvn tycho-versions:set-version -DnewVersion=1.0.3-SNAPSHOT</code></li>
+</ol>
+<p>Once the release has passed, the following must be done:</p>
+<ol>
+<li>upload p2update.zip* to https://dist.apache.org/repos/dist/release/sling/</li>
+<li>upload unzipped update site to https://dist.apache.org/repos/dist/release/sling/eclipse/1.0.2</li>
+<li>upload the source bundle to https://dist.apache.org/repos/dist/release/sling/eclipse/1.0.2<ol>
+<li>create GPG signatures and checksums for all uploaded jars ( see below for a script example )</li>
+</ol>
+</li>
+<li>update https://dist.apache.org/repos/dist/release/sling/eclipse/composite{Content,Artifacts}.xml to point version 1.0.2</li>
+<li>archive the old artifact versions but leave pointers to archive.apache.org, using compositeArtifacts.xml/compositeContent.xml , with a single child entry pointing to https://archive.apache.org/dist/sling/eclipse/1.0.0/</li>
+</ol>
+<p>The GPG signatures can be generated using a script such as the one below</p>
+<table class="codehilitetable"><tr><td class="linenos"><div class="linenodiv"><pre> 1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13</pre></div></td><td class="code"><div class="codehilite"><pre><span class="c">#!/bin/bash</span>
+
+<span class="k">for </span>jarfile in <span class="sb">`</span>find . -name <span class="se">\*</span>.jar -o -name <span class="se">\*</span>.zip | xargs basename<span class="sb">`</span> ; <span class="k">do</span>
+<span class="k"> if</span> <span class="o">[</span> ! -f <span class="nv">$jarfile</span>.md5 <span class="o">]</span> ; <span class="k">then</span>
+<span class="k"> </span>md5sum <span class="nv">$jarfile</span> > <span class="nv">$jarfile</span>.md5
+ <span class="k">fi</span>
+<span class="k"> if</span> <span class="o">[</span> ! -f <span class="nv">$jarfile</span>.sha1 <span class="o">]</span> ; <span class="k">then</span>
+<span class="k"> </span>sha1sum <span class="nv">$jarfile</span> > <span class="nv">$jarfile</span>.sha1
+ <span class="k">fi</span>
+<span class="k"> if</span> <span class="o">[</span> ! -f <span class="nv">$jarfile</span>.asc <span class="o">]</span> ; <span class="k">then</span>
+<span class="k"> </span>gpg --detach-sign -a <span class="nv">$jarfile</span>
+ <span class="k">fi</span>
+<span class="k">done</span>
+</pre></div>
+</td></tr></table>
+
<h2 id="appendix-a-create-and-add-your-key-to-httpspeopleapacheorgkeysgroupslingasc">Appendix A: Create and Add your key to <a href="https://people.apache.org/keys/group/sling.asc">https://people.apache.org/keys/group/sling.asc</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>
@@ -425,8 +486,9 @@ Then go to the CMS at <a href="https://c
update your checkout and then publish the site.</p>
</li>
</ol>
+<h2 id="appendix-d-releasing-the-sling-ide-tooling">Appendix D: Releasing the Sling IDE Tooling</h2>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1627982 by cziegeler on Sat, 27 Sep 2014 15:55:45 +0000
+ Rev. 1631127 by rombert on Sat, 11 Oct 2014 21:30:57 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project