sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r868155 - in /websites/staging/sis/trunk/content: ./ release-announce.txt release-management.html
Date Tue, 02 Jul 2013 13:17:43 GMT
Author: buildbot
Date: Tue Jul  2 13:17:43 2013
New Revision: 868155

Log:
Staging update by buildbot for sis

Modified:
    websites/staging/sis/trunk/content/   (props changed)
    websites/staging/sis/trunk/content/release-announce.txt
    websites/staging/sis/trunk/content/release-management.html

Propchange: websites/staging/sis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jul  2 13:17:43 2013
@@ -1 +1 @@
-1498043
+1498915

Modified: websites/staging/sis/trunk/content/release-announce.txt
==============================================================================
--- websites/staging/sis/trunk/content/release-announce.txt (original)
+++ websites/staging/sis/trunk/content/release-announce.txt Tue Jul  2 13:17:43 2013
@@ -7,6 +7,6 @@ The release can be obtained from the Apa
 
 Release notes are available at - https://svn.apache.org/repos/asf/sis/tags/sis-$VERSION/RELEASE_NOTES
 
-Apache SIS is a software framework providing API’s, sophisticated  server-side tools,
and graphical user interfaces to construct, execute, control and manage long running applications
and workflows on distributed computing resources. Apache SIS builds on general concepts of
service oriented computing, distributed messaging, and workflow composition and orchestration.
+Apache SIS is a spatial framework that enables better representation of coordinates for searching,
data clustering, archiving, or any other relevant spatial needs. SIS provides data structures
for geographic data and associated metadata along with methods to manipulate those data structures.
The SIS metadata module forms the base of the library and enables the creation of metadata
objects which comply with the ISO 19115 metadata model and which can be read from or written
to ISO 19139 compliant XML documents.
 
 For general information on Apache SIS, please visit the project website: http://sis.apache.org/

Modified: websites/staging/sis/trunk/content/release-management.html
==============================================================================
--- websites/staging/sis/trunk/content/release-management.html (original)
+++ websites/staging/sis/trunk/content/release-management.html Tue Jul  2 13:17:43 2013
@@ -93,7 +93,7 @@
       <div class="span9">
       	<section id="content" class="row">
         	<article class="span12">
-          	<p>Releases are crucial aspects for an apache project and following the
guidelines is very important. The <a href="http://www.apache.org/dev/release.html">Release
FAQ</a> describes the foundation wide policies. The following instructions walkthrough
SIS specific release steps. </p>
+          	<p>Releases are crucial aspects for an apache project and following the
guidelines is very important. The <a href="http://www.apache.org/dev/release.html">Release
FAQ</a> describes the foundation wide policies. The following instructions walkthrough
SIS specific release steps.</p>
 <p><a name="release-setup"></a></p>
 <h3 id="one-time-release-management-setup">One time release management setup</h3>
 <p>This section describes release management configuration steps, if you have previously
configured these steps, jump directly to <a href="#release-process">Release Process</a>.</p>
@@ -105,18 +105,18 @@
 <p><a name="gpg-key"></a></p>
 <h4 id="generate-gpg-key">Generate GPG key</h4>
 <p>The releases have to be signed by public key cryptography signatures. Detailed instructions
on why releases have to be signed are provided on <a href="http://www.apache.org/dev/release-signing.html">Release
Signing</a> page.
-The popular software used Open Pretty Good Privacy (OpenPGP) is the GPG. The <a href="http://www.apache.org/dev/openpgp.html">GPG
instructions</a> list out detailed steps on managing your keps.</p>
-<p>The steps can be summerized as: </p>
+The popular software used Open Pretty Good Privacy (OpenPGP) is the GPG. The <a href="http://www.apache.org/dev/openpgp.html">GPG
instructions</a> list out detailed steps on managing your keys.</p>
+<p>The steps can be summarized as:</p>
 <ul>
 <li>Generate 4096 bits RSA key pair using gpg: <code>gpg --gen-key</code>.</li>
 <li>Export the public key: <code>gpg --list-sigs &lt;Real Name&gt; &amp;&amp;
gpg --armor -- export &lt;Real Name&gt;</code></li>
 <li>Upload the public key to <a href="http://pgp.surfnet.nl:11371/">SURFNET PGP</a>
or <a href="http://pgp.mit.edu/">MIT PGP</a> servers.</li>
-<li>Have your key signed by atleast three apache commiters, <a href="http://www.apache.org/dev/release-signing.html#key-signing-party">key
signing</a> and <a href="http://people.apache.org/~henkp/trust/">Henk Penning</a>
websites provide instructions.</li>
+<li>Have your key signed by at least three apache commiters, <a href="http://www.apache.org/dev/release-signing.html#key-signing-party">key
signing</a> and <a href="http://people.apache.org/~henkp/trust/">Henk Penning</a>
websites provide instructions.</li>
 <li>Add the signed public key to the KEYS file on <a href="https://dist.apache.org/repos/dist/release/sis/">SIS
Dist SVN</a>.</li>
 </ul>
 <p>For reference, the steps to sign a key:</p>
 <ul>
-<li>The person whom you know in person provides you his key, usually this happens at
key signing party where you can verify each others ID's. </li>
+<li>The person whom you know in person provides you his key, usually this happens at
key signing party where you can verify each others ID's.</li>
 <li>Fetch the key <code>gpg --keyserver &lt;keyserver&gt; --recv-keys
&lt;Key_ID&gt;</code> an example key server is pgp.mit.edu</li>
 <li>Sign the key <code>gpg --sign-key &lt;Key_ID&gt;</code></li>
 <li>Upload the key back to the server <code>gpg --keyserver &lt;keyserver&gt;
--send-key &lt;Key_ID&gt;</code></li>
@@ -125,13 +125,13 @@ The popular software used Open Pretty Go
 <h4 id="maven-configuration-nexus-setup">Maven Configuration &amp; Nexus Setup</h4>
 <ul>
 <li>SIS requires Maven 3 or later to build and release</li>
-<li>It is encouraged to use maven's password encryption capabilities and set the gpg
password in 
+<li>It is encouraged to use maven's password encryption capabilities and set the gpg
password in
 ~/.m2/settings.xml. Detailed instructions are at <a href="http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env">Publishing
Maven Artifacts</a><ul>
-<li>Make sure both the apache.snapshots.https and apache.releases.https are configured
coreectly. </li>
+<li>Make sure both the apache.snapshots.https and apache.releases.https are configured
correctly.</li>
 </ul>
 </li>
 <li>Performing release will require maven to run series of commands, the heapsize has
to be increased to avoid out of memory exceptions.</li>
-<li>Bash Shell: <code>export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=256m"</code>.
</li>
+<li>Bash Shell: <code>export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=256m"</code>.</li>
 <li>C Shell: <code>setenv MAVEN_OPTS "-Xmx1024m -XX:MaxPermSize=256m"</code>.</li>
 </ul>
 <p><a name="release-process"></a></p>
@@ -141,7 +141,7 @@ The popular software used Open Pretty Go
 <p>Before performing the following release steps, ensure the <a href="#release-setup">Release
Setup</a> steps have been performed.</p>
 </li>
 <li>
-<p>Ensure the source is ready for release. Verify:   </p>
+<p>Ensure the source is ready for release. Verify:</p>
 <ul>
 <li>Cleanup JIRA so the Fix Version in issues resolved since the last release includes
this release version correctly.</li>
 <li>Ensure all open issues are resolved before proceeding further, close all resolved
issues.</li>
@@ -165,7 +165,7 @@ The popular software used Open Pretty Go
 
 </li>
 <li>
-<p>Verify the source has the required license headers before trying to release: </p>
+<p>Verify the source has the required license headers before trying to release:</p>
 <div class="codehilite"><pre>`<span class="n">mvn</span> <span
class="o">-</span><span class="n">P</span> <span class="n">pedantic</span>
<span class="n">verify</span> <span class="o">-</span><span class="n">DskipTests</span><span
class="p">=</span><span class="n">true</span>`
 </pre></div>
 
@@ -182,7 +182,7 @@ The popular software used Open Pretty Go
 <li>Release version</li>
 <li>SCM release tag</li>
 <li>New development version</li>
-<li>GPG Passprhase - On a Mac if the passphrase is stored in keychain, the passphrase
is not prompted. </li>
+<li>GPG Passprhase - On a Mac if the passphrase is stored in keychain, the passphrase
is not prompted.</li>
 </ul>
 <p><em>If you cancel a release:prepare before it updates the pom.xml versions,
then use the release:clean goal to just remove the extra files that were created.</em></p>
 <p>The Maven release plugin checks for SNAPSHOT dependencies in pom's. It will not
complete the prepare goal until all SNAPSHOT dependencies are resolved.</p>
@@ -191,13 +191,13 @@ The popular software used Open Pretty Go
 <p>Verify that the release process completed as expected</p>
 <ul>
 <li>The release plugin will create pom.xml.tag files which contain the changes that
would have been committed to SVN. The only differences between pom.xml.tag and it's corresponding
pom.xml file should be the version number.</li>
-<li>If other formatting changes have been made you should review the changes and then
commit them <code>svn commit -m "fixing formatting for release"</code>  </li>
+<li>If other formatting changes have been made you should review the changes and then
commit them <code>svn commit -m "fixing formatting for release"</code></li>
 <li>Check release.properties and make sure that the scm properties have the right version.
Sometimes the scm location can be the previous version not the next version.</li>
 <li>Verify signatures (<a href="#verify_signatures">Verifying release signatures</a>)</li>
 </ul>
 </li>
 <li>
-<p>Once any failures or required updates have been committed to svn, rollback the release
prepare files:  </p>
+<p>Once any failures or required updates have been committed to svn, rollback the release
prepare files:</p>
 <div class="codehilite"><pre>`<span class="n">mvn</span> <span
class="o">-</span><span class="n">P</span> <span class="n">apache</span><span
class="o">-</span><span class="n">release</span> <span class="n">release</span><span
class="p">:</span><span class="n">rollback</span>`
 </pre></div>
 
@@ -215,7 +215,7 @@ The popular software used Open Pretty Go
 <p>Perform the release</p>
 <ul>
 <li>
-<p>This step will create a maven staging repository and site for use in testing and
voting. </p>
+<p>This step will create a maven staging repository and site for use in testing and
voting.</p>
 <div class="codehilite"><pre>`<span class="n">mvn</span> <span
class="n">release</span><span class="p">:</span><span class="n">perform</span>
<span class="o">-</span><span class="n">Papache</span><span class="o">-</span><span
class="n">release</span>`
 </pre></div>
 
@@ -233,7 +233,7 @@ The popular software used Open Pretty Go
 <p>Verify the HTML links in site are correct</p>
 </li>
 <li>
-<p>Verify the staged artifacts in the nexus repo     </p>
+<p>Verify the staged artifacts in the nexus repo</p>
 <ul>
 <li>https://repository.apache.org/index.html</li>
 <li>Staging repositories (under Build Promotion) --&gt; Name column --&gt;
org.apache.sis</li>
@@ -274,7 +274,7 @@ The popular software used Open Pretty Go
 
 </li>
 <li>
-<p>Create the directory for ${project.version} and RC{number} within it. The RC number
corresponds to the current release attempt. </p>
+<p>Create the directory for ${project.version} and RC{number} within it. The RC number
corresponds to the current release attempt.</p>
 </li>
 <li>Copy the source and binaries into dist area.<ul>
 <li>Copy the source and binaries into the development dist RC area created above.</li>
@@ -308,7 +308,7 @@ The popular software used Open Pretty Go
 <p>Finalizing a release</p>
 <ol>
 <li>
-<p>The artificats in the repository are not yet mirrored and available for maven to
download. Promote the staged nexus artifacts, but releasing them.   </p>
+<p>The artificats in the repository are not yet mirrored and available for maven to
download. Promote the staged nexus artifacts, but releasing them.</p>
 <ul>
 <li>https://repository.apache.org/index.html</li>
 <li>Staging repositories (under Build Promotion) --&gt; Name column --&gt;
org.apache.sis</li>
@@ -316,7 +316,7 @@ The popular software used Open Pretty Go
 </ul>
 </li>
 <li>
-<p>Checkin the source and binary artifcats into distribution svn which will be pulled
by all mirrors within 24 hours. The dist/dev svn is not mirrored, but the dist/release is.
  </p>
+<p>Checkin the source and binary artifcats into distribution svn which will be pulled
by all mirrors within 24 hours. The dist/dev svn is not mirrored, but the dist/release is.</p>
 <ul>
 <li><code>svn copy https://dist.apache.org/repos/dist/dev/sis/${project.version}/RC{number}
https://dist.apache.org/repos/dist/release/sis/${project.version}  -m "Committing SIS Source
and Binary Release for ${project.name}-${project.version}</code></li>
 </ul>
@@ -352,7 +352,7 @@ The popular software used Open Pretty Go
 <p>Announcing the release</p>
 <ul>
 <li>Make a news announcement on the SIS homepage.</li>
-<li>Make an announcement about the release on the dev@sis.apache.org, users@sis.apache.org,
and announce@apache.org. </li>
+<li>Make an announcement about the release on the dev@sis.apache.org, users@sis.apache.org,
and announce@apache.org.</li>
 <li>Sample announce <a href="release-announce.txt">email</a>.</li>
 </ul>
 </li>
@@ -368,11 +368,11 @@ The popular software used Open Pretty Go
 <p>$ svn del https://svn.apache.org/repos/asf/sis/tags/${project.version} -m "deleting
tag from rolled back release"</p>
 </li>
 <li>
-<p>Revert the svn to old version <code>mvn -P apache-release release:rollback</code></p>
+<p>Revert the svn to old version <code>mvn -P apache-release release:rollback</code>
+5.</p>
 </li>
-<li></li>
 <li>
-<p>Delete the build artifacts on people &amp; www           </p>
+<p>Delete the build artifacts on people &amp; www</p>
 <ul>
 <li>$ rm -rfv /www/people.apache.org/builds/sis/${project.version}</li>
 </ul>
@@ -398,7 +398,7 @@ The popular software used Open Pretty Go
 <p>On unix platforms and mac's download all source and binary artifacts into a new
directory and cd to the download directory.</p>
 <div class="codehilite"><pre>  for file in `find . -type f -iname &#39;*.asc&#39;`
   do
-      gpg --verify <span class="cp">${</span><span class="nb">file</span><span
class="cp">}</span> 
+      gpg --verify <span class="cp">${</span><span class="nb">file</span><span
class="cp">}</span>
   done
 </pre></div>
 



Mime
View raw message