You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wookie.apache.org by bu...@apache.org on 2012/11/27 10:54:47 UTC
svn commit: r839743 [3/6] - in /websites/staging/wookie/trunk/content: ./
css/ docs/ docs/developer/ docs/developer/features/ docs/releases/
docs/tutorial/ docs/tutorial/lib/ docs/tutorial/lib/s5/
docs/tutorial/lib/s5/ui/ docs/tutorial/lib/s5/ui/defaul...
Added: websites/staging/wookie/trunk/content/docs/developer/release-configuration.html
==============================================================================
--- websites/staging/wookie/trunk/content/docs/developer/release-configuration.html (added)
+++ websites/staging/wookie/trunk/content/docs/developer/release-configuration.html Tue Nov 27 09:54:44 2012
@@ -0,0 +1,205 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/wookie/css/wookie.css" rel="stylesheet" type="text/css">
+ <link href="/wookie/css/code.css" rel="stylesheet" type="text/css">
+ <title>Apache Wookie (Incubating) - Release Configuration</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+ <div id="banner">
+ <img alt="Apache Wookie (Incubating)" src="/wookie/images/logo.png"/>
+ <h1 class="title">Release Configuration</h1>
+ </div>
+
+ <div id="navigation">
+ <h1 id="general">General</h1>
+<ul>
+<li><a href="/wookie/index.html">Home</a></li>
+<li><a href="/wookie/news.html">News</a></li>
+<li><a href="/wookie/docs/download.html">Download</a></li>
+<li><a href="http://incubator.apache.org/projects/wookie.html">Incubator page</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+</ul>
+<h1 id="documentation">Documentation</h1>
+<ul>
+<li><a href="/wookie/docs/download.html">Download and Quickstart</a></li>
+<li><a href="/wookie/docs/admin.html">Server Admin</a></li>
+<li><a href="/wookie/docs/embedding.html">Embedding</a></li>
+<li><a href="/wookie/docs/shindig.html">Integrating with Shindig</a></li>
+<li><a href="/wookie/docs/widgets.html">Building widgets</a></li>
+<li><a href="/wookie/docs/faq.html">FAQ</a></li>
+<li><a href="/wookie/docs/api.html">API Reference</a></li>
+</ul>
+<h1 id="community">Community</h1>
+<ul>
+<li><a href="/wookie/get-involved.html">Get Involved</a></li>
+<li><a href="/wookie/mailing-lists.html">Mailing Lists</a></li>
+<li><a href="/wookie/people.html">People</a></li>
+</ul>
+<h1 id="development">Development</h1>
+<ul>
+<li><a href="/wookie/docs/source.html">Getting Started</a></li>
+<li><a href="/wookie/docs/developer/running.html">Running</a></li>
+<li><a href="/wookie/docs/templates.html">Widget Templates</a></li>
+<li><a href="/wookie/docs/developer/features.html">Extension Features</a></li>
+<li><a href="/wookie/docs/developer/widgets.html">Deploying Widgets</a></li>
+<li><a href="/wookie/docs/develop.html">Environment</a></li>
+<li><a href="/wookie/docs/developer/release-management.html">Release Management</a></li>
+<li><a href="/wookie/docs/developer/issues.html">Issue Tracker</a></li>
+<li><a href="/wookie/docs/developer/index.html">Management</a></li>
+<li><a href="/wookie/docs/developer/parser.html">W3C Widget Parser</a></li>
+</ul>
+<h1 id="asf">ASF</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 id="release-configuration-and-setup">Release configuration and setup</h1>
+<p>These setup steps only need to be performed on a particular machine once.</p>
+<p>Developers using Linux workstations can skip over the references to Cygwin. If using Windows, install cygwin, including Utils/gnupg and Net/openssh packages.</p>
+<h2 id="create-and-install-a-ssh-key">Create and install a SSH key</h2>
+<div class="codehilite"><pre><span class="n">Open</span> <span class="n">a</span> <span class="n">shell</span> <span class="n">window</span><span class="o">.</span> <span class="n">If</span> <span class="n">using</span> <span class="n">Windows</span><span class="p">,</span> <span class="nb">open</span> <span class="n">a</span> <span class="n">cygwin</span> <span class="n">window</span><span class="o">.</span>
+<span class="n">Use</span> <span class="n">ssh</span><span class="o">-</span><span class="n">keygen</span> <span class="n">to</span> <span class="n">create</span> <span class="n">an</span> <span class="n">SSH</span> <span class="n">key</span><span class="o">.</span>
+</pre></div>
+
+
+<p>Follow the latest steps and guides on the <a href="http://www.apache.org/dev/openpgp.html#generate-key">ASF website</a> as you should NOT be using SHA1 and new keys MUST be at least 4096 bits.</p>
+<div class="codehilite"><pre> <span class="nv">$</span> <span class="nv">ssh</span><span class="o">-</span><span class="n">keygen</span> <span class="o">-</span><span class="n">t</span> <span class="n">rsa</span> <span class="o">-</span><span class="n">b</span> <span class="mi">4096</span>
+</pre></div>
+
+
+<p>Program defaults should be fine. No passphrase is required for the ssh key generation. The keys will be saved in ~/.ssh/id_dsa (private) and ~/.ssh/id_dsa.pub (public).</p>
+<p>See <a href="http://www.networknewz.com/networknewz-10-20030707AuthenticatingbyPublicKeyOpenSSH.html">Authenticating By Public Key (OpenSSH)</a> for a good description on why and how to perform this task.</p>
+<ol>
+<li>
+<p>SCP your SSH public key ~/.ssh/id_dsa.pub created in last step to ~/id_dsa.pub on people.apache.org.</p>
+<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">cd</span> <span class="o">~/.</span><span class="n">ssh</span>
+<span class="nv">$</span> <span class="nv">scp</span> <span class="n">id_dsa</span><span class="o">.</span><span class="n">pub</span> <span class="nv">@people</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org:id_dsa</span><span class="o">.</span><span class="n">pub</span>
+<span class="nv">$</span> <span class="nv">You</span> <span class="n">will</span> <span class="n">be</span> <span class="n">prompted</span> <span class="k">for</span> <span class="n">your</span> <span class="n">password</span><span class="o">.</span>
+</pre></div>
+
+
+</li>
+<li>
+<p>Use ssh to login to people.apache.org</p>
+<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">cd</span> <span class="o">~</span>
+<span class="nv">$</span> <span class="nv">ssh</span> <span class="nv">@people</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span>
+</pre></div>
+
+
+</li>
+</ol>
+<p>At this point, you will still be prompted for your password.</p>
+<ol>
+<li>
+<p>Create a ~/.ssh folder in your home directory on people.apache.org and change its file mode to 700.</p>
+<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">mkdir</span> <span class="o">~/.</span><span class="n">ssh</span>
+<span class="nv">$</span> <span class="nv">chmod</span> <span class="mi">700</span> <span class="o">~/.</span><span class="n">ssh</span>
+</pre></div>
+
+
+</li>
+<li>
+<p>Move or append ~/id_dsa.pub to ~/.ssh/authorized_keys and change its file mode to 600.</p>
+<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">mv</span> <span class="o">~</span><span class="sr">/id_dsa.pub ~/</span><span class="o">.</span><span class="n">ssh</span><span class="o">/</span><span class="n">authorized_keys</span>
+<span class="nv">$</span> <span class="nv">chmod</span> <span class="mi">600</span> <span class="o">~</span><span class="sr">/.ssh/</span><span class="n">authorized_keys</span>
+</pre></div>
+
+
+</li>
+</ol>
+<p><em>Each public key in the authorized_keys spans only one line.
+ For example: "ssh-dss AAAAB3NzaC1kc3MAAA ..... agBmmfZ9uAbSqA== dsa-key-20071107"
+ '#' in the first column is a comment line.</em></p>
+<ol>
+<li>
+<p>Exit out of this ssh session.</p>
+</li>
+<li>
+<p>Start a new ssh session. No login should be required this time due to the private ssh key on your local box matching up with the public ssh key in your home directory (~/.ssh).</p>
+<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">ssh</span> <span class="nv">@people</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span>
+</pre></div>
+
+
+<p>If you are still prompted for a password, then you have not set up the ssh keys properly. Review the steps above and ensure that all of the steps were followed properly. Or, maybe the instructions are still not quite right and they still need some adjusting. In that case, please update the instructions accordingly.</p>
+</li>
+</ol>
+<p>You can alternatively use putty to create and install your ssh key. The instructions <a href="http://people.apache.org/~gmcdonald/ssh_putty.html">here</a> outline the process.</p>
+<h2 id="create-a-gpg-key">Create a GPG key</h2>
+<p>Apache recommend using GNU Privacy Guard to generate keys and sign artifacts.</p>
+<ol>
+<li>
+<p>Open a shell window. If using Windows, open a cygwin window.</p>
+</li>
+<li>
+<p>Generate a key-pair with gpg, using default key kind ("RSA and RSA") and keys size (4096).</p>
+<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">gpg</span> <span class="o">--</span><span class="n">gen</span><span class="o">-</span><span class="n">key</span>
+</pre></div>
+
+
+<p>The program's default values should be fine. For the "Real Name" enter your full name (ie. Stan Programmer). For the "e-mail address" enter your apache address (ie. sprogrammer@apache.org). You will also be required to enter a "passphrase" for the GPG key generation. Keep track of this as you will need this for the Release processing.</p>
+</li>
+<li>
+<p>The generated keys are stored in $HOME/.gnupg or %HOME%\Application Data\gnupg subdirectory.</p>
+</li>
+<li>
+<p>Save the content in this subdirectory to a safe media. This contains your private key used to sign all the Wookie release materials.</p>
+</li>
+<li>
+<p>Backup your home directory to another media ||</p>
+</li>
+<li>
+<p>Add your public key to the <a href="https://svn.apache.org/repos/asf/incubator/wookie/KEYS">SVN repository</a>. See the commands describe at the beginning of this KEYS file to perform this task. The gpg key-pair is used to sign the published artifacts for the Wookie releases.</p>
+<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">gpg</span> <span class="o">--</span><span class="n">list</span><span class="o">-</span><span class="n">sigs</span> <span class="o">&&</span> <span class="n">gpg</span> <span class="o">--</span><span class="n">armor</span> <span class="o">--</span> <span class="n">export</span>
+</pre></div>
+
+
+<p>The <a href="https://svn.apache.org/repos/asf/incubator/wookie/KEYS">KEYS</a> file is updated via normal svn commit procedures.</p>
+</li>
+<li>
+<p>Submit your public key to a key server. E.g. <a href="http://pgp.mit.edu/">MIT</a></p>
+</li>
+<li>
+<p>Following the instructions in http://people.apache.org/~henkp/trust/ and ask multiple (at least 3) current Apache committers to sign your public key.</p>
+</li>
+</ol>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2011-2012 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/wookie/trunk/content/docs/developer/release-discuss.txt
==============================================================================
--- websites/staging/wookie/trunk/content/docs/developer/release-discuss.txt (added)
+++ websites/staging/wookie/trunk/content/docs/developer/release-discuss.txt Tue Nov 27 09:54:44 2012
@@ -0,0 +1,15 @@
+To: wookie-dev@incubator.apache.org
+Subject: [DISCUSS] Apache Wookie *.*.* Release Candidate
+
+Discussion thread for vote on *.*.* release candidate.
+
+For more information on the release process, checkout -
+http://www.apache.org/dev/release.html
+
+Some of the things to check before voting are:
+- can you run the demo binaries
+- can you build the contents of source-release.zip and svn tag
+- do all of the staged jars/zips contain the required LICENSE, NOTICE and
+DISCLAIMER files
+- are all of the staged artifacts signed and the signature verifiable
+- is the signing key in the project's KEYS file and on a public server
Added: websites/staging/wookie/trunk/content/docs/developer/release-management.html
==============================================================================
--- websites/staging/wookie/trunk/content/docs/developer/release-management.html (added)
+++ websites/staging/wookie/trunk/content/docs/developer/release-management.html Tue Nov 27 09:54:44 2012
@@ -0,0 +1,107 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/wookie/css/wookie.css" rel="stylesheet" type="text/css">
+ <link href="/wookie/css/code.css" rel="stylesheet" type="text/css">
+ <title>Apache Wookie (Incubating) - Release Management</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+ <div id="banner">
+ <img alt="Apache Wookie (Incubating)" src="/wookie/images/logo.png"/>
+ <h1 class="title">Release Management</h1>
+ </div>
+
+ <div id="navigation">
+ <h1 id="general">General</h1>
+<ul>
+<li><a href="/wookie/index.html">Home</a></li>
+<li><a href="/wookie/news.html">News</a></li>
+<li><a href="/wookie/docs/download.html">Download</a></li>
+<li><a href="http://incubator.apache.org/projects/wookie.html">Incubator page</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+</ul>
+<h1 id="documentation">Documentation</h1>
+<ul>
+<li><a href="/wookie/docs/download.html">Download and Quickstart</a></li>
+<li><a href="/wookie/docs/admin.html">Server Admin</a></li>
+<li><a href="/wookie/docs/embedding.html">Embedding</a></li>
+<li><a href="/wookie/docs/shindig.html">Integrating with Shindig</a></li>
+<li><a href="/wookie/docs/widgets.html">Building widgets</a></li>
+<li><a href="/wookie/docs/faq.html">FAQ</a></li>
+<li><a href="/wookie/docs/api.html">API Reference</a></li>
+</ul>
+<h1 id="community">Community</h1>
+<ul>
+<li><a href="/wookie/get-involved.html">Get Involved</a></li>
+<li><a href="/wookie/mailing-lists.html">Mailing Lists</a></li>
+<li><a href="/wookie/people.html">People</a></li>
+</ul>
+<h1 id="development">Development</h1>
+<ul>
+<li><a href="/wookie/docs/source.html">Getting Started</a></li>
+<li><a href="/wookie/docs/developer/running.html">Running</a></li>
+<li><a href="/wookie/docs/templates.html">Widget Templates</a></li>
+<li><a href="/wookie/docs/developer/features.html">Extension Features</a></li>
+<li><a href="/wookie/docs/developer/widgets.html">Deploying Widgets</a></li>
+<li><a href="/wookie/docs/develop.html">Environment</a></li>
+<li><a href="/wookie/docs/developer/release-management.html">Release Management</a></li>
+<li><a href="/wookie/docs/developer/issues.html">Issue Tracker</a></li>
+<li><a href="/wookie/docs/developer/index.html">Management</a></li>
+<li><a href="/wookie/docs/developer/parser.html">W3C Widget Parser</a></li>
+</ul>
+<h1 id="asf">ASF</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 id="release-management">Release Management</h1>
+<p>Release artifacts are distributed via the Apache Nexus repository for both SNAPSHOT and versioned releases.
+In addition to Nexus, a source and standalone binary and WAR archive release will be made available via the <a href="http://www.apache.org/dist/incubator/wookie/">Apache Incubator Distribution Area</a>.</p>
+<p>To familiarize yourself with the notions and requirements for releasing artifacts, please checkout the Apache Release FAQ.</p>
+<h3 id="apache-wookie-incubating-release-guidelines">Apache Wookie (Incubating) Release Guidelines</h3>
+<ol>
+<li><a href="/wookie/docs/developer/release-configuration.html">Release Manager Configuration Guide</a></li>
+<li><a href="/wookie/docs/developer/release-overview.html">Release Overview</a></li>
+<li><a href="/wookie/docs/developer/release-process.html">Release Process</a></li>
+<li><a href="/wookie/docs/developer/release-testing.html">Release Testing</a></li>
+</ol>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2011-2012 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/wookie/trunk/content/docs/developer/release-overview.html
==============================================================================
--- websites/staging/wookie/trunk/content/docs/developer/release-overview.html (added)
+++ websites/staging/wookie/trunk/content/docs/developer/release-overview.html Tue Nov 27 09:54:44 2012
@@ -0,0 +1,250 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/wookie/css/wookie.css" rel="stylesheet" type="text/css">
+ <link href="/wookie/css/code.css" rel="stylesheet" type="text/css">
+ <title>Apache Wookie (Incubating) - Release Overview</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+ <div id="banner">
+ <img alt="Apache Wookie (Incubating)" src="/wookie/images/logo.png"/>
+ <h1 class="title">Release Overview</h1>
+ </div>
+
+ <div id="navigation">
+ <h1 id="general">General</h1>
+<ul>
+<li><a href="/wookie/index.html">Home</a></li>
+<li><a href="/wookie/news.html">News</a></li>
+<li><a href="/wookie/docs/download.html">Download</a></li>
+<li><a href="http://incubator.apache.org/projects/wookie.html">Incubator page</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+</ul>
+<h1 id="documentation">Documentation</h1>
+<ul>
+<li><a href="/wookie/docs/download.html">Download and Quickstart</a></li>
+<li><a href="/wookie/docs/admin.html">Server Admin</a></li>
+<li><a href="/wookie/docs/embedding.html">Embedding</a></li>
+<li><a href="/wookie/docs/shindig.html">Integrating with Shindig</a></li>
+<li><a href="/wookie/docs/widgets.html">Building widgets</a></li>
+<li><a href="/wookie/docs/faq.html">FAQ</a></li>
+<li><a href="/wookie/docs/api.html">API Reference</a></li>
+</ul>
+<h1 id="community">Community</h1>
+<ul>
+<li><a href="/wookie/get-involved.html">Get Involved</a></li>
+<li><a href="/wookie/mailing-lists.html">Mailing Lists</a></li>
+<li><a href="/wookie/people.html">People</a></li>
+</ul>
+<h1 id="development">Development</h1>
+<ul>
+<li><a href="/wookie/docs/source.html">Getting Started</a></li>
+<li><a href="/wookie/docs/developer/running.html">Running</a></li>
+<li><a href="/wookie/docs/templates.html">Widget Templates</a></li>
+<li><a href="/wookie/docs/developer/features.html">Extension Features</a></li>
+<li><a href="/wookie/docs/developer/widgets.html">Deploying Widgets</a></li>
+<li><a href="/wookie/docs/develop.html">Environment</a></li>
+<li><a href="/wookie/docs/developer/release-management.html">Release Management</a></li>
+<li><a href="/wookie/docs/developer/issues.html">Issue Tracker</a></li>
+<li><a href="/wookie/docs/developer/index.html">Management</a></li>
+<li><a href="/wookie/docs/developer/parser.html">W3C Widget Parser</a></li>
+</ul>
+<h1 id="asf">ASF</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 id="introduction">Introduction</h1>
+<p>This document is an overview of the release process for Apache Wookie (Incubating). </p>
+<h1 id="release-phases">Release Phases</h1>
+<p>This section summarises each phase in the release process. There are more details for each phase in the sections below.</p>
+<ol>
+<li>Development<ol>
+<li>Analyze Open Issues</li>
+<li>Issue Fixing - ongoing - all issues should be resolved or moved</li>
+<li>Issue Validation - all resolved issues must be checked as being truly fixed and thus marker as verified</li>
+<li>Collect committer public keys</li>
+<li>Licence Audit and Legal Audit - including headers, dependencies, LICENCE and NOTICE files</li>
+</ol>
+</li>
+<li>Release Candidate<ol>
+<li>Licence Audit and Legal Audit - including headers, dependencies, LICENCE and NOTICE files</li>
+<li>Documentation â Check installation and build documentation for accuracy, create status document, create release notes</li>
+<li>Create release branch on SVN â sign binaries, permissions</li>
+<li>Test, test, test! (repeat from previous step until no problems emerge in test)</li>
+</ol>
+</li>
+<li>Prepare for release<ol>
+<li>Write the release announcement (with approval from press@)</li>
+<li>Tag the release branch </li>
+<li>Build the release files</li>
+<li>Signing of release files</li>
+</ol>
+</li>
+<li>Vote on release</li>
+<li>Request approval from Incubator PCM</li>
+<li>Release<ol>
+<li>Upload to incubator distributions site</li>
+<li>Wait for mirroring to take place </li>
+<li>Announce the release</li>
+</ol>
+</li>
+</ol>
+<h2 id="development">Development</h2>
+<p>These steps are to be carried out in the run up to a relase. They are, in the main, an ongoing activity
+rather than a part of the release cycle itself.</p>
+<h3 id="open-issues">Open Issues</h3>
+<p>A list of outstanding issues is generated from Jira. This list is posted to the project developer list
+with suggestions to either implement for the release or postpone for the next release. After community
+discussion JIRA is updated accordingly.</p>
+<p>When deciding whether to implement an issue for this release be aware of taking on too much. It is more
+important to get a release out than to complete all features. Release early, release often.</p>
+<p>Once complete this process gives a clear definition of what will be included in the release and allows
+timescales to be estimated.</p>
+<h3 id="issue-fixing-and-verification">Issue Fixing and Verification</h3>
+<p>Each issue for the release to be fixed then the fixes to be tested, reviewed and accepted.</p>
+<h3 id="signatures">Signatures</h3>
+<p>The committers for the project need to provide public keys for the release, each person who submits a
+key needs to keep the private key safe. These will be included with the release in a KEYS file. The
+process of creating a key pair should be consistent across the committers. Apache recommend using
+GNU Privacy Guard to generate keys and sign the artifacts.</p>
+<p>Committers without a code signing key should generate one - RSA 4096 bits</p>
+<p>If committers have a DSA or RSA key of less than 2048 bits then a new one should be generated for
+signing releases, again using RSA 4096 bit.</p>
+<p>For committers who already have an RSA key of 2048 bits or more some configuration of their client
+to avoid weaknesses are required. Instructions on how to do this can be found
+<a href="http://www.apache.org/dev/openpgp.html#sha1">here</a>.</p>
+<h4 id="web-of-trust">Web of Trust</h4>
+<p>Once individuals have generated keys, opportunities should be taken (where possible)
+to join the Apache Web of Trust. First the keys should be uploaded to a public key
+server (is there a recommended one we should use?). Next key signing: if conferences
+are attended or events where there are other Apache developers and there are key
+signing parties.</p>
+<h3 id="license-audit-and-legal-audit">License Audit and Legal Audit</h3>
+<p>There is a need to check all licenses manually, including headers in source files etc...
+The licenses for all libraries should be in place. LICENSE and NOTICE files need to
+be created. The Release Audit Tool (RAT) <a href="http://ci.apache.org/projects/wookie/rat-output.html">report</a>
+is helpful in this regard.</p>
+<p>In licenses/all_licenses.txt record the details of all dependencies; this should include not
+only any libraries referenced directly in ivy.xml, but also any dependencies of features, connectors
+and widgets. It is not, however, necessary to document licenses of secondary dependencies.</p>
+<p>The LICENSE file should contain our license and the licenses for all dependencies underneath.<br />
+The NOTICE file contains the following text modified for our project and the notices from
+dependencies underneath.</p>
+<p>Apache PRODUCT_NAME
+Copyright yyyy The Apache Software Foundation</p>
+<p>This product includes software developed at
+The Apache Software Foundation (http://www.apache.org/).</p>
+<h2 id="release-candidate">Release Candidate</h2>
+<p>This is the first real phase of the release process.</p>
+<h3 id="documentation">Documentation</h3>
+<p>The installation and build documentation which is included with the release needs to be
+checked for accuracy. Other documentation is maintained online and can be modified when
+required. When we announce the release it would be good to review the documentation for
+accuracy and usability. The status document can be generated from the issue tracker with
+some introduction. Release notes need to be created including the standard incubator disclaimer.</p>
+<h3 id="release-tag">Release Tag</h3>
+<p>When we reach code freeze a tag should be created in which the release is built and
+signed. This will allow continued development on trunk. The tag can also be used to
+maintain the release, but any changes or fixes there need to be merged back into trunk.
+There is a detailed description here of an approach similar to this. When built and
+signed the tag should be considered the release candidate for testing.</p>
+<h3 id="build-the-release-candidate">Build the release candidate</h3>
+<p>The release candidate files are built from the release branch. The files to be provided are:</p>
+<ul>
+<li>Source distribution</li>
+<li>Standalone distribution</li>
+<li>WAR distribution</li>
+<li>W3C Parser subproject (Nexus artifact)</li>
+<li>Java Connector subproject (Nexus artifact)</li>
+<li>WAR self contained (Nexus artifact)</li>
+</ul>
+<h3 id="testing">Testing</h3>
+<p>The final build should be tested on all supported platforms, we provide a <a href="releaseTesting.html">minimal testing
+script</a> for your to follow.<br />
+</p>
+<p>If any tests identify problems the community needs to decide if this is a blocker to the release or not.
+If not a blocker the issue should be documented, if a blocker it should be fixed and a new
+release candidate is built.</p>
+<h2 id="prepare-for-release">Prepare for release</h2>
+<p>This is where we build the actual release.</p>
+<h3 id="write-release-announcement">Write release announcement</h3>
+<p>The release announcement is written in cooperation with the press@ list.</p>
+<h3 id="tag-the-release-branch">Tag the release branch</h3>
+<p>The release branch is tagged with the release number.</p>
+<h3 id="build-release-files">Build release files</h3>
+<p>All release files are built from the tag. Release files are:</p>
+<ul>
+<li>Source distribution</li>
+<li>Standalone distribution</li>
+<li>WAR distribution</li>
+<li>W3C Parser subproject (Nexus artifact)</li>
+<li>Java Connector subproject (Nexus artifact)</li>
+<li>WAR self contained (Nexus artifact)</li>
+</ul>
+<h3 id="signing-of-release-files">Signing of release files</h3>
+<p>A minimum of three committers must sign the release using their keys avilable in SVN.</p>
+<h2 id="vote-on-the-release">Vote on the release</h2>
+<p>The community votes on the release. Since the release candidate has been thoroughly tested
+by the community this should be a formality. However, it is an important formality as it
+indicates that the project management committee have verified the legal integrity of the
+release.</p>
+<p>If you are a PMC member you should not vote +1 unless you are satisfied that the software is,
+to the best of your knowledge, ready for release.</p>
+<h2 id="request-incubator-approval">Request incubator approval</h2>
+<p>Whilst in the incubator the project needs to have official approvel from the Incubator PMC.
+As with the community vote this should be a formality, however, many incubator PMC
+members will check the legal status of the release as an added precaution.</p>
+<h2 id="release">Release</h2>
+<p>All there is to do now is get the release out there.</p>
+<h3 id="upload-to-incubator-distribution-site">Upload to incubator distribution site</h3>
+<p>Once you have uploaded the files to the incubator distribution site you will need to check
+permissions and wait for mirroring to take place.</p>
+<h3 id="announce-the-release">Announce the release</h3>
+<p>The release announcement needs to be posted to:</p>
+<ul>
+<li>announce@</li>
+<li>wookie-users@</li>
+<li>wookie-dev@</li>
+<li>project website</li>
+</ul>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2011-2012 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/wookie/trunk/content/docs/developer/release-process.html
==============================================================================
--- websites/staging/wookie/trunk/content/docs/developer/release-process.html (added)
+++ websites/staging/wookie/trunk/content/docs/developer/release-process.html Tue Nov 27 09:54:44 2012
@@ -0,0 +1,513 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/wookie/css/wookie.css" rel="stylesheet" type="text/css">
+ <link href="/wookie/css/code.css" rel="stylesheet" type="text/css">
+ <title>Apache Wookie (Incubating) - Release Process</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+ <div id="banner">
+ <img alt="Apache Wookie (Incubating)" src="/wookie/images/logo.png"/>
+ <h1 class="title">Release Process</h1>
+ </div>
+
+ <div id="navigation">
+ <h1 id="general">General</h1>
+<ul>
+<li><a href="/wookie/index.html">Home</a></li>
+<li><a href="/wookie/news.html">News</a></li>
+<li><a href="/wookie/docs/download.html">Download</a></li>
+<li><a href="http://incubator.apache.org/projects/wookie.html">Incubator page</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+</ul>
+<h1 id="documentation">Documentation</h1>
+<ul>
+<li><a href="/wookie/docs/download.html">Download and Quickstart</a></li>
+<li><a href="/wookie/docs/admin.html">Server Admin</a></li>
+<li><a href="/wookie/docs/embedding.html">Embedding</a></li>
+<li><a href="/wookie/docs/shindig.html">Integrating with Shindig</a></li>
+<li><a href="/wookie/docs/widgets.html">Building widgets</a></li>
+<li><a href="/wookie/docs/faq.html">FAQ</a></li>
+<li><a href="/wookie/docs/api.html">API Reference</a></li>
+</ul>
+<h1 id="community">Community</h1>
+<ul>
+<li><a href="/wookie/get-involved.html">Get Involved</a></li>
+<li><a href="/wookie/mailing-lists.html">Mailing Lists</a></li>
+<li><a href="/wookie/people.html">People</a></li>
+</ul>
+<h1 id="development">Development</h1>
+<ul>
+<li><a href="/wookie/docs/source.html">Getting Started</a></li>
+<li><a href="/wookie/docs/developer/running.html">Running</a></li>
+<li><a href="/wookie/docs/templates.html">Widget Templates</a></li>
+<li><a href="/wookie/docs/developer/features.html">Extension Features</a></li>
+<li><a href="/wookie/docs/developer/widgets.html">Deploying Widgets</a></li>
+<li><a href="/wookie/docs/develop.html">Environment</a></li>
+<li><a href="/wookie/docs/developer/release-management.html">Release Management</a></li>
+<li><a href="/wookie/docs/developer/issues.html">Issue Tracker</a></li>
+<li><a href="/wookie/docs/developer/index.html">Management</a></li>
+<li><a href="/wookie/docs/developer/parser.html">W3C Widget Parser</a></li>
+</ul>
+<h1 id="asf">ASF</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 id="release-process">Release Process</h1>
+<p>This document is an overview of the release process for Apache Wookie (Incubating).
+Wookie uses a series of ant scripts coupled together with Apache Ivy to allow automatic building of the code into its various release artifacts.
+It can also be used to automatically sign binaries and deploy artifacts to the Nexus Repository.</p>
+<p>Make sure the <a href="release-configuration.html">Release Setup</a> steps have been performed.</p>
+<h2 id="what-exactly-do-we-build-and-release">What exactly do we build and release?</h2>
+<p>You should familiarize yourself with the ant scripts in the project as they are used to create the artifacts. We will go over the specific tasks for generating them
+in more detail later.</p>
+<p>Note the following 3 artifacts that are to be generated. Eventually these should be made available to download from <a href="http://www.apache.org/dist/incubator/wookie/">http://www.apache.org/dist/incubator/wookie/</a></p>
+<ol>
+<li>A source release (apache-wookie-VERSION-src.zip) (and also a tar.gz version)<ul>
+<li>this is for users who wish to download the code and build it themselves</li>
+</ul>
+</li>
+<li>A standalone release (apache-wookie-VERSION-standalone.zip) (and also a tar.gz version)<ul>
+<li>this is aimed at first time/casual users and incorparates a preconfigured Jetty and Derby DB to work out of the box</li>
+</ul>
+</li>
+<li>A WAR release (apache-wookie-VERSION-war.zip) (and also a tar.gz version)<ul>
+<li>this is aimed towards users who have an existing server setup (their own tomcat/mysql system for example)
+and want to deploy it alongside their own existing web applications. The bundled documentation is geared towards
+configuring it for tomcat/mysql but it also includes scripts for other databases.</li>
+</ul>
+</li>
+</ol>
+<p>Additionally there are 3 Nexus artifacts to generate. Eventually these should be made available from the Nexus Repository.</p>
+<ol>
+<li>A Nexus artifact of the wookie connector subproject (wookie-java-connector-VERSION.jar)<ul>
+<li>this is for users who want to incorporate the connector part of wookie only as a jar via maven</li>
+</ul>
+</li>
+<li>A Nexus artifact of the wookie parser subproject (wookie-parser-VERSION.jar)<ul>
+<li>this is for users who want to incorporate the w3c widget parser part of wookie only as a jar via maven</li>
+</ul>
+</li>
+<li>A Nexus artifact of the wookie WAR (wookie-VERSION.war)<ul>
+<li>this is for users who want to include a self contained version of the wookie.war in their own projects via maven.
+(the difference between this and #3 is that this one is configured & bundled with Derby DB.)</li>
+</ul>
+</li>
+</ol>
+<h2 id="steps-to-making-a-release">Steps to making a release</h2>
+<h3 id="1-resolve-outstanding-jira-issues-marked-against-this-planned-release">1. Resolve Outstanding JIRA issues marked against this planned release</h3>
+<ol>
+<li>Analyse open issues</li>
+<li>Issues should be FIXED and verified to ensure they are truly fixed and thus marked as verified</li>
+<li>Alternatively, in some cases open issues can be moved to the next planned release</li>
+<li>No open issues should remain against this intended release before continuing<ul>
+<li>The only exception to this is if an issue directly addresses the build process, such as "create build for release" type issue.</li>
+</ul>
+</li>
+</ol>
+<h3 id="2-communicate-with-committers-regarding-new-release">2. Communicate with committers regarding new release</h3>
+<p>Send an email to wookie-dev@incubator.apache.org and start a vote to discuss whether everybody agrees it is okay to go ahead and make a release.
+Ideally we'd want a +3 from the committers, but this is not always possible.<br />
+</p>
+<h3 id="3-check-all-licenses-notices-and-other-related-files">3. Check all Licenses, notices and other related files</h3>
+<ol>
+<li>
+<p>Check the following files found at the root of the trunk. (They are bundled with all the builds, except in the case of LICENSE and NOTICE, which are build specific)</p>
+<ol>
+<li>README - this is usually the first file a user will read when they download either the source or binary versions of wookie.
+This file usually will not need to be updated very often, but as it points to other files and explains some of the different builds, it should be checked for accuracy.</li>
+<li>RELEASE_NOTES - this must be updated with the list of issues addressed since the last release.<br />
+This can be obtained from the wookie JIRA by selecting all issues addressed for this planned version.</li>
+<li>UPGRADING - this must be updated if there were any significant changes made to wookie since the last release.
+Examples of this are - changes to the database which means that users may have to manually migrate data using scripts or where a major overhaul of the user interface OR API means users would have to change/update their current practices for using those parts of wookie</li>
+<li>NOTICE - this should be checked to make sure any new components added to wookie since the last release are mentioned. Note: the actual licences for these go into the LICENSE file.</li>
+<li>NEW_AND_NOTEWORTHY - this should be checked and updated to point out and mention any new features in wookie since the last release, that are deemed significant.</li>
+<li>BUILDING - this describes how to build wookie from the source. This should be checked for accuracy, but will probably not change very often.</li>
+<li>LICENSE - this file contains references to all the licenses of the third party and contributed libaries and code used in wookie.<br />
+Any new libraries and code added since the last release must have their licences added here. The main exception here is an existing Apache Software Foundation library, which does not need to be included.</li>
+</ol>
+</li>
+<li>
+<p>Check the licences and notices found under /trunk/etc/release/ (Note: some of the builds have specific LICENCE and NOTICE files)</p>
+<ol>
+<li>/trunk/etc/release/maven/subprojects/LICENCE. This licence file is bundled with all the maven artifacts
+(except the maven WAR artifact) and should only contain the apache license. (It is found in in the /META-INF folder of a generated .jar file)</li>
+<li>/trunk/etc/release/maven/subprojects/NOTICE. This notice file is bundled with all the maven artifacts
+(except the maven WAR artifact) and should only contain the apache license references. (It is found in in the /META-INF folder of a generated .jar file)</li>
+<li>/trunk/etc/release/maven/war/LICENSE. This license file is bundled with the maven WAR artifact only.
+(It is found in in the /META-INF folder of a generated .war file).</li>
+<li>/trunk/etc/release/maven/war/NOTICE. This notice file is bundled with the maven WAR artifact only.
+(It is found in in the /META-INF folder of a generated .war file).</li>
+<li>/trunk/etc/release/standalone/LICENSE. This license file is bundled with the standalone build only. (It is found at the root of the generated standalone build)</li>
+<li>/trunk/etc/release/standalone/NOTICE. This notice file is bundled with the standalone build only. (It is found at the root of the generated standalone build)</li>
+<li>/trunk/etc/release/standalone/STANDALONE_BUILD_NOTES. This should not change very often, but a quick read through is recommended to make sure nothing has changed.
+ (It is found at the root of the generated standalone build)</li>
+<li>/trunk/etc/release/war/LICENSE. This license file is bundled with the war build only. (It is found at the root of the generated war build)</li>
+<li>/trunk/etc/release/war/NOTICE. This notice file is bundled with the war build only. (It is found at the root of the generated war build)</li>
+<li>/trunk/etc/release/war/WAR_BUILD_NOTES. This should not change very often, but a quick read through is recommended to make sure nothing has changed.
+(It is found at the root of the generated war build)</li>
+</ol>
+</li>
+</ol>
+<h3 id="4-check-all-files-for-license-headers">4. Check all files for license headers</h3>
+<p>Use the <a href="http://ci.apache.org/projects/wookie/rat-output.html">Release Audit Tool (RAT)</a> report to find any missing license headers. Fix any missing entries.</p>
+<h3 id="5-update-all-references-to-snapshot-in-the-properties-files-and-update-the-pom-templates">5. Update all references to SNAPSHOT in the properties files and update the pom-templates</h3>
+<ol>
+<li>
+<p>Find the version reference in the following files. Update it in each case removing the '-SNAPSHOT' at the end, so that it reads for example '0.10.0-incubating'. Note that in the top-level ivy.xml there are actually three references you need to change, including the dependencies on the Connector and Parser.</p>
+<ul>
+<li>/build.properties</li>
+<li>/ivy.xml</li>
+<li>/connector/java/build.properties</li>
+<li>/connector/java/ivy.xml</li>
+<li>/modules/jcr/build.properties</li>
+<li>/modules/jcr/ivy.xml</li>
+<li>/parser/java/build.properties</li>
+<li>/parser/java/ivy.xml</li>
+<li>/src/widgetserver.properties</li>
+<li>/etc/release/runsignatures.bat</li>
+</ul>
+</li>
+<li>
+<p>Update the 3 pom-template.xml files so that the scm values reference the tag version to be created</p>
+<ul>
+<li>/pom-template.xml</li>
+</ul>
+<p>Find...</p>
+<div class="codehilite"><pre> <span class="nt"><scm></span>
+ <span class="nt"><connection></span>scm:svn:http://svn.apache.org/repos/asf/incubator/wookie/trunk<span class="nt"></connection></span>
+ <span class="nt"><developerConnection></span>scm:svn:https://svn.apache.org/repos/asf/incubator/wookie/trunk/<span class="nt"></developerConnection></span>
+ <span class="nt"><url></span>http://svn.apache.org/viewvc/incubator/wookie/trunk/<span class="nt"></url></span>
+ <span class="nt"></scm></span>
+</pre></div>
+
+
+<p>...and update it (with correct version number) to read...</p>
+<div class="codehilite"><pre><span class="nt"><scm></span>
+ <span class="nt"><connection></span>scm:svn:http://svn.apache.org/repos/asf/incubator/wookie/tags/<span class="cp">${</span><span class="n">project</span><span class="o">.</span><span class="n">version</span><span class="cp">}</span><span class="nt"></connection></span>
+ <span class="nt"><developerConnection></span>scm:svn:https://svn.apache.org/repos/asf/incubator/wookie/tags/<span class="cp">${</span><span class="n">project</span><span class="o">.</span><span class="n">version</span><span class="cp">}</span>/<span class="nt"></developerConnection></span>
+ <span class="nt"><url></span>http://svn.apache.org/viewvc/incubator/wookie/tags/<span class="cp">${</span><span class="n">project</span><span class="o">.</span><span class="n">version</span><span class="cp">}</span>/<span class="nt"></url></span>
+<span class="nt"></scm></span>
+</pre></div>
+
+
+<p>Where ${project.version} is going to be your tag name.</p>
+<p>Do the same with the following two files...</p>
+<ul>
+<li>/connector/java/pom-template.xml</li>
+<li>/parser/java/pom-template.xml</li>
+</ul>
+</li>
+<li>
+<p>Commit your changes back to svn.</p>
+</li>
+</ol>
+<h3 id="6-inform-committers-of-temporary-code-freeze">6. Inform committers of temporary code freeze</h3>
+<p>Send an email to wookie-dev@incubator.apache.org informing that you are about to tag the trunk.
+ (just in case there are commits while you are doing it. It only takes a minute to tag it, so not a long freeze.)</p>
+<h3 id="7-create-a-tag-of-the-current-trunk-state">7. Create a tag of the current trunk state.</h3>
+<ol>
+<li>Ensure you have checked out a clean copy of the trunk from svn.</li>
+<li>In Eclipse select the wookie root folder and right click. Choose team -> Tag...</li>
+<li>A dialog appears.</li>
+<li>In the Tag: box enter the release version number i.e. '0.10.0-incubating'<ul>
+<li>use the same version here as you entered in step (5.2) when updating the pom-template files</li>
+</ul>
+</li>
+<li>In the Comment box enter something sensible i.e. 'wookie release 0.10.0-incubating'</li>
+<li>Click ok to create the tag.</li>
+<li>If you tick the "Start working in the tag" box, the tag will be created and your local copy will update to the tagged version</li>
+<li>Verify the tag was created correctly & in the right place. <ul>
+<li>In the Eclipse SVN Repository Exploring view you can navigate to svn.apache.org/repos/asf/incubator/wookie/tags/ and make sure the tag exists.</li>
+</ul>
+</li>
+</ol>
+<h3 id="8-roll-version-number-forward-in-all-properties-files-in-the-trunk">8. Roll version number forward in all properties files in the trunk.</h3>
+<ol>
+<li>If you haven't already, switch back to the trunk. </li>
+<li>Find all the files listed in step (#5.1) above.</li>
+<li>Update all the entries to the next version-SNAPSHOT - i.e. 0.11.0-incubating-SNAPSHOT</li>
+<li>Update the 3 pom-template.xml files in step (#5.2) above so that they point back at the trunk again</li>
+<li>Commit your changes</li>
+</ol>
+<h3 id="9-inform-commiters-that-you-have-finished">9. Inform commiters that you have finished</h3>
+<p>Send an email to wookie-dev@incubator.apache.org informing that you have tagged the trunk for the build and that the trunk has now rolled to the next version. (which also means the freeze has been lifted)</p>
+<h3 id="10-run-the-build-script">10. Run the build script</h3>
+<ol>
+<li>Switch back to the created tag version. Run the ant task 'build-release-all' found in the root build.xml file<ul>
+<li>either use eclipse to run it or use 'ant build-release-all' on the command line at the wookie root folder</li>
+</ul>
+</li>
+<li>
+<p>This should generate a new folder at the root of wookie called 'release' containing the following structure...</p>
+<div class="codehilite"><pre>release
+ <span class="cp">${</span><span class="n">project</span><span class="o">.</span><span class="n">version</span><span class="cp">}</span>-incubating
+ binary
+ standalone
+ apache-wookie-<span class="cp">${</span><span class="n">project</span><span class="o">.</span><span class="n">version</span><span class="cp">}</span>-incubating-standalone.tar.gz
+ apache-wookie-<span class="cp">${</span><span class="n">project</span><span class="o">.</span><span class="n">version</span><span class="cp">}</span>-incubating-standalone.zip
+ rat-report.txt
+ war
+ apache-wookie-<span class="cp">${</span><span class="n">project</span><span class="o">.</span><span class="n">version</span><span class="cp">}</span>-incubating-war.tar.gz
+ apache-wookie-<span class="cp">${</span><span class="n">project</span><span class="o">.</span><span class="n">version</span><span class="cp">}</span>-incubating-war.zip
+ rat-report.txt
+ source
+ apache-wookie-<span class="cp">${</span><span class="n">project</span><span class="o">.</span><span class="n">version</span><span class="cp">}</span>-incubating-src.tar.gz
+ apache-wookie-<span class="cp">${</span><span class="n">project</span><span class="o">.</span><span class="n">version</span><span class="cp">}</span>-incubating-src.zip
+ rat-report.txt
+ runsignatures.bat
+</pre></div>
+
+
+</li>
+<li>
+<p>The rat-report.txt files are for your reference and can be removed when checked. <br />
+</p>
+</li>
+<li>Open a command prompt and run the 'runsignatures.bat' file<ul>
+<li>(AUTHOR NOTE: we need to either also supply a .sh version of this or better still automate it)</li>
+<li>This creates the ASC signatures, MD5 and SHA files needed for file verification</li>
+<li>This will only work if you have already followed the steps outlined in the <a href="release-configuration.html">Release Setup</a></li>
+</ul>
+</li>
+<li>Manually check the ASC, MD5 and SHA files are correct<ul>
+<li>The generated ASC files are automatically checked when you run the 'runsignatures.bat' (see how in the file), but the SHA and MD5 are not</li>
+<li>These can be checked using openssl at the command prompt, for example...<ul>
+<li>'openssl sha512 <buildname.zip>' - should generate same key on screen as found in the buildname.zip.sha file</li>
+<li>'openssl md5 <buildname.zip>' - should generate same key on screen as found in the buildname.zip.md5 file</li>
+</ul>
+</li>
+</ul>
+</li>
+<li>Open each build artifact and test that it...<ul>
+<li>contains the correct NOTICE & LICENSE files where appropriate</li>
+<li>the source builds will build from the command prompt, using 'ant compile-core'</li>
+<li>the standalone builds will run when you click it's startup script (May need to add executable permissions on mac/linux)</li>
+<li>examine the WAR build for integrity (also ideally drop the WAR file into a preconfigured tomcat/mysql instance on your machine to make sure it deploys/works okay)</li>
+</ul>
+</li>
+</ol>
+<h3 id="11-upload-the-artifacts-to-peopleapacheorg">11. Upload the artifacts to people.apache.org</h3>
+<ol>
+<li>Make sure you delete the 3 rat-report.txt files (otherwise the next stage will upload them)</li>
+<li>
+<p>From the 'wookie/release' folder run the following to upload the generated build folder and artifacts...</p>
+<div class="codehilite"><pre>scp -r <span class="cp">${</span><span class="n">project</span><span class="o">.</span><span class="n">version</span><span class="cp">}</span> <span class="cp">${</span><span class="n">user</span><span class="o">.</span><span class="n">name</span><span class="cp">}</span>@people.apache.org:/www/people.apache.org/builds/incubator/wookie/
+</pre></div>
+
+
+<p>...substituting the ${project.version} with the folder name of the generated artifacts i.e...</p>
+<div class="codehilite"><pre><span class="n">scp</span> <span class="o">-</span><span class="n">r</span> <span class="o">.</span><span class="sr">/0.10.0-incubating joebloggs@people.apache.org:/</span><span class="n">www</span><span class="sr">/people.apache.org/</span><span class="n">builds</span><span class="sr">/incubator/</span><span class="n">wookie</span><span class="o">/</span>
+</pre></div>
+
+
+<p>(Note: the pscp utility comes with putty, rather than scp)</p>
+</li>
+<li>
+<p>Verify they are downloadable from http://people.apache.org/builds/incubator/wookie</p>
+</li>
+</ol>
+<h3 id="12-upload-the-nexus-release-artifacts">12. Upload the Nexus release artifacts</h3>
+<ol>
+<li>
+<p>If you use eclipse to run your ant tasks then right click the /build.xml</p>
+<ul>
+<li>choose run as -> ant build...</li>
+<li>
+<p>highlight the "Main" tab and in the "Arguments" panel add the following</p>
+<div class="codehilite"><pre><span class="o">-</span><span class="n">Duser</span><span class="o">.</span><span class="n">name</span><span class="o">=</span><span class="s">"My Name"</span> <span class="o">-</span><span class="n">Dupload</span><span class="o">.</span><span class="n">user</span><span class="o">=</span><span class="n">your_apache_userid</span> <span class="o">-</span><span class="n">Dupload</span><span class="o">.</span><span class="n">password</span><span class="o">=</span><span class="n">your_svn_password</span> <span class="o">-</span><span class="n">Dpgp</span><span class="o">.</span><span class="n">password</span><span class="o">=</span><span class="n">your_pgp_password</span> <span class="o">-</span><span class="n">Dpgp</span><span class="o">.</span><span class="n">keyId</span><span class="o">=</span><span class="n">your_pgp_keyid</span>
+</pre></div>
+
+
+</li>
+</ul>
+<p>(substituting your details where applicable)</p>
+<ul>
+<li>click apply.</li>
+<li>To check/preview the Nexus artifacts locally first run 'ant publish-local' found in the root build.xml file</li>
+<li>this publishes all artifacts (parser, connector and self contained WAR) locally only and can be found under ${user.home}.m2\repository\org\apache\wookie</li>
+<li>Once again check to make sure the correct LICENSE and NOTICE files appear in each /META-INF folder found within each archive</li>
+<li>
+<p>When you are happy the generated files are okay, either run the following ant task at the command prompt to deploy to Nexus...</p>
+<p>ant publish-maven-release-artifacts publish-subproject-artifacts-to-release-repo -Duser.name="My Name" -Dupload.user=your_apache_userid -Dupload.user=your_apache_userid -Dupload.password=your_svn_password -Dpgp.password=your_pgp_password -Dpgp.keyId=your_pgp_keyid</p>
+</li>
+</ul>
+<p>or if you have completed step (1.) above, simply right click the root build.xml and choose to run 'publish-maven-release-artifacts' and 'publish-subproject-artifacts-to-release-repo'
+(AUTHOR NOTE: we need to merge these ant tasks into 1 call)</p>
+</li>
+<li>
+<p>Verify the staged artifacts in the Nexus repository</p>
+<ul>
+<li>https://repository.apache.org/index.html</li>
+<li>Staging repositories (under Build Promotion) --> Name column --> org.apache.wookie</li>
+<li>Navigate through the artifact tree and make sure that all javadoc, sources, tests, jars, ... have .asc (GPG signature) and .md5 files. </li>
+<li>See http://people.apache.org/~henkp/repo/faq.html and http://www.apache.org/dev/release-signing.html#openpgp-ascii-detach-sig</li>
+</ul>
+</li>
+<li>
+<p>Close the Nexus staging repository</p>
+<ul>
+<li>https://repository.apache.org/index.html</li>
+<li>Staging repositories (under Build Promotion) --> Name column --> org.apache.wookie</li>
+<li>click checkbox for the open staging repo (org.apache.wookie-XXX) and press Close in the menu bar.</li>
+</ul>
+</li>
+</ol>
+<h3 id="13-put-the-release-candidate-up-for-a-vote-on-the-wookie-dev-list">13. Put the release candidate up for a vote on the wookie-dev list</h3>
+<ol>
+<li>Create a VOTE email thread on wookie-dev@ to record votes as replies, like <a href="release-vote.txt">this</a></li>
+<li>Create a DISCUSS email thread on wookie-dev@ for any vote questions, <a href="release-discuss.txt">this</a></li>
+<li>
+<p>Perform a review of the release and cast your vote. See the following for more details on Apache releases</p>
+<p><a href="http://www.apache.org/dev/release.html">http://www.apache.org/dev/release.html</a></p>
+</li>
+<li>
+<p>A -1 vote does not necessarily mean that the vote must be redone, however it is usually a good idea to rollback the release if a -1 vote is received. </p>
+<ul>
+<li>See - Recovering from a vetoed release</li>
+</ul>
+</li>
+<li>
+<p>After the vote has been open for at least 72 hours, has at least three +1 PMC votes and no -1 votes, then post the results to the vote thread</p>
+<ul>
+<li>reply to the initial email and prepend to the original subject "[RESULT]"</li>
+<li>Include a list of everyone who voted +1, 0 or -1.</li>
+</ul>
+</li>
+</ol>
+<h3 id="14-put-the-release-candidate-up-for-a-vote-on-the-incubator-general-list">14. Put the release candidate up for a vote on the incubator general list</h3>
+<ol>
+<li>Create similar VOTE email on the general@incubator.apache.org list, like <a href="release-vote-general.txt">this</a> <ul>
+<li>Depending on how many binding +1 IPMC votes the release candidates received, you may need to wait for additional ones from the general list</li>
+</ul>
+</li>
+<li>After the vote has been open for at least 72 hours and has at least three +1 IPMC votes (in total) then post the results to the vote thread<ul>
+<li>reply to the initial email and prepend to the original subject "[RESULT]"</li>
+<li>Include a list of everyone who voted +1, 0 or -1.</li>
+</ul>
+</li>
+<li>NOTE: For the release candidate to be successful it must at least have received at least 3 +1 IPMC votes combined from both wookie-dev and general.</li>
+</ol>
+<h3 id="15-finalizing-a-release">15. Finalizing a release</h3>
+<ol>
+<li>Promote the staged nexus artifacts<ul>
+<li>https://repository.apache.org/index.html</li>
+<li>Staging repositories (under Build Promotion) --> Name column --> org.apache.wookie</li>
+<li>click checkbox of the closed staging repo (org.apache.wookie-***) and select Release.</li>
+</ul>
+</li>
+<li>
+<p>Copy the release artifacts over to the distribution area</p>
+<ul>
+<li>login to people.apache.org and copy across the build folder</li>
+</ul>
+<p>cp -r /www/people.apache.org/builds/incubator/wookie/${project.version}-incubating /www/www.apache.org/dist/incubator/wookie</p>
+<p>(replacing the version name accordingly)</p>
+<ul>
+<li>verify the folder and contents copied across okay.</li>
+<li>Delete the staged version (cleanup)</li>
+<li>login to people.apache.org (if not already) and delete the old staged release </li>
+</ul>
+<p>rm -rfv /www/people.apache.org/builds/incubator/wookie/${project.version}-incubating</p>
+<p>(replacing the version name accordingly)</p>
+</li>
+<li>
+<p>Update the staged website</p>
+<ul>
+<li>Update the downloads page and source page to add new version using the mirrored URLs</li>
+<li>Add New and Noteworthy to docs/releases</li>
+<li>Add entry to News about the new release</li>
+<li>Modify the URL for the prior release to the archived URL for the release</li>
+</ul>
+</li>
+<li>
+<p>Publish the website</p>
+<ul>
+<li>Wait 24hrs after committing releases for mirrors to replicate</li>
+<li>Publish updates to the download page</li>
+</ul>
+</li>
+</ol>
+<h3 id="16-update-jira">16. Update JIRA</h3>
+<ol>
+<li>Update the JIRA versions page to close all issues, mark the version as "released", and set the date to the date that the release was approved.
+ You may also need to make a new release entry for the next release.</li>
+</ol>
+<h3 id="17-announcing-the-release">17. Announcing the release</h3>
+<ol>
+<li>Make a news announcement on the Wookie News page.</li>
+<li>Make an announcement about the release on the following lists <ul>
+<li>wookie-dev@incubator.apache.org</li>
+<li>wookie-users@incubator.apache.org</li>
+<li>announce@apache.org</li>
+</ul>
+</li>
+</ol>
+<h3 id="18-recovering-from-a-vetoed-release">18. Recovering from a vetoed release</h3>
+<ol>
+<li>
+<p>Reply to the initial vote email and prepend to the original subject -</p>
+<p>[CANCELED]</p>
+</li>
+<li>
+<p>Delete the svn tag you created in step (7) above. Either use eclipse to do this or via command prompt</p>
+<p>$ svn del https://svn.apache.org/repos/asf/incubator/wookie/tags/${project.version} -m "deleting tag from rolled back release"</p>
+</li>
+<li>
+<p>Delete the build artifacts on people</p>
+<p>$ rm -rfv /www/people.apache.org/builds/incubator/wookie/${project.version}</p>
+</li>
+<li>
+<p>Drop the nexus staging repo</p>
+<ul>
+<li>https://repository.apache.org/index.html</li>
+<li>Enterprise --> Staging</li>
+<li>Staging tab --> Name column --> org.apache.wookie
+ -Right click on the closed staging repo (org.apache.wookie-XXX) and select Drop.</li>
+</ul>
+</li>
+<li>
+<p>Make the required updates that caused the vote to be canceled during the next release cycle</p>
+</li>
+</ol>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2011-2012 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/wookie/trunk/content/docs/developer/release-testing.html
==============================================================================
--- websites/staging/wookie/trunk/content/docs/developer/release-testing.html (added)
+++ websites/staging/wookie/trunk/content/docs/developer/release-testing.html Tue Nov 27 09:54:44 2012
@@ -0,0 +1,195 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/wookie/css/wookie.css" rel="stylesheet" type="text/css">
+ <link href="/wookie/css/code.css" rel="stylesheet" type="text/css">
+ <title>Apache Wookie (Incubating) - Testing a release</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+ <div id="banner">
+ <img alt="Apache Wookie (Incubating)" src="/wookie/images/logo.png"/>
+ <h1 class="title">Testing a release</h1>
+ </div>
+
+ <div id="navigation">
+ <h1 id="general">General</h1>
+<ul>
+<li><a href="/wookie/index.html">Home</a></li>
+<li><a href="/wookie/news.html">News</a></li>
+<li><a href="/wookie/docs/download.html">Download</a></li>
+<li><a href="http://incubator.apache.org/projects/wookie.html">Incubator page</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+</ul>
+<h1 id="documentation">Documentation</h1>
+<ul>
+<li><a href="/wookie/docs/download.html">Download and Quickstart</a></li>
+<li><a href="/wookie/docs/admin.html">Server Admin</a></li>
+<li><a href="/wookie/docs/embedding.html">Embedding</a></li>
+<li><a href="/wookie/docs/shindig.html">Integrating with Shindig</a></li>
+<li><a href="/wookie/docs/widgets.html">Building widgets</a></li>
+<li><a href="/wookie/docs/faq.html">FAQ</a></li>
+<li><a href="/wookie/docs/api.html">API Reference</a></li>
+</ul>
+<h1 id="community">Community</h1>
+<ul>
+<li><a href="/wookie/get-involved.html">Get Involved</a></li>
+<li><a href="/wookie/mailing-lists.html">Mailing Lists</a></li>
+<li><a href="/wookie/people.html">People</a></li>
+</ul>
+<h1 id="development">Development</h1>
+<ul>
+<li><a href="/wookie/docs/source.html">Getting Started</a></li>
+<li><a href="/wookie/docs/developer/running.html">Running</a></li>
+<li><a href="/wookie/docs/templates.html">Widget Templates</a></li>
+<li><a href="/wookie/docs/developer/features.html">Extension Features</a></li>
+<li><a href="/wookie/docs/developer/widgets.html">Deploying Widgets</a></li>
+<li><a href="/wookie/docs/develop.html">Environment</a></li>
+<li><a href="/wookie/docs/developer/release-management.html">Release Management</a></li>
+<li><a href="/wookie/docs/developer/issues.html">Issue Tracker</a></li>
+<li><a href="/wookie/docs/developer/index.html">Management</a></li>
+<li><a href="/wookie/docs/developer/parser.html">W3C Widget Parser</a></li>
+</ul>
+<h1 id="asf">ASF</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <p>These are instructions to help community members with testing new releases.</p>
+<p>TODO - out of date instructions - need to update! - References to UI have been depricated</p>
+<h1 id="test-environment">Test Environment</h1>
+<p>Ideally the client will access from a different network machine to the server.</p>
+<h1 id="testing-the-build-and-run-scripts">Testing the Build and Run Scripts</h1>
+<p>There are three different types of build to test for release. All should be available in the latest release branch
+on svn and/or in the staging area as declared on the wookie-dev list.</p>
+<ul>
+<li>download the appropriate build (all builds should be tested, not just one)</li>
+<li>for source and standalone builds run in standalone mode using the run target in ant</li>
+<li>for the war build deploy the war in your chosen container</li>
+<li>check index page responds</li>
+</ul>
+<h1 id="widget-gallery">Widget Gallery</h1>
+<ul>
+<li>open a new browser window on the server home page</li>
+<li>click view widget gallery</li>
+<li>pick a random widget and click "Demo"</li>
+<li>ensure the widget behaves as expected</li>
+<li>refresh the page</li>
+<li>ensure the widget behaves as expected</li>
+<li>repeat above for at least one other widget (more is better)</li>
+</ul>
+<h1 id="features">Features</h1>
+<ul>
+<li>visit the widget gallery again</li>
+<li>select the Freeder widget (or a widget that you know uses a feature0</li>
+<li>ensure that the widget retrieves some RSS items and displays them correctly</li>
+</ul>
+<h1 id="administration">Administration</h1>
+<h2 id="widget-tests">Widget tests</h2>
+<ul>
+<li>open a new browser window on the server home page</li>
+<li>click "Administration menu"</li>
+<li>enter username and password (default is java, java)</li>
+<li>verify that there are no errors logged for deployed widgets (there may be some warnings about IE compatibility)</li>
+<li>click "View existing widgets"</li>
+<li>expand a few widgets and ensure page behaves as expected</li>
+</ul>
+<h2 id="widget-deployment">Widget Deployment</h2>
+<ul>
+<li>click back button</li>
+<li>click "add new widget"</li>
+<li>upload a test widget (we should provide a simple test widget
+ in SVN that is packaged but not bundled with the release) </li>
+<li>repeat the "Widget Gallery" tests above with the test widget</li>
+<li>stop the server using CTRL-C</li>
+<li>restart the server and verify the uploaded widget is still present</li>
+</ul>
+<h2 id="gadget-deployment">Gadget Deployment</h2>
+<p>Note that Gadget deployment will only work if you have also installed Shindig
+according to the instructions for Integrating Wookie with Shindig. If you
+haven't installed and configured Shindig, skip this step.</p>
+<div class="codehilite"><pre><span class="o">*</span> <span class="n">Repeat</span> <span class="n">the</span> <span class="n">Widget</span> <span class="n">Deployment</span> <span class="n">above</span> <span class="n">but</span> <span class="n">with</span> <span class="n">a</span> <span class="n">Gadget</span> <span class="n">rather</span> <span class="n">than</span> <span class="n">a</span> <span class="n">Widget</span>
+</pre></div>
+
+
+<h2 id="remove-widget">Remove Widget</h2>
+<div class="codehilite"><pre><span class="o">*</span> <span class="n">Click</span> <span class="s">"Remove widget"</span>
+<span class="o">*</span> <span class="n">find</span> <span class="n">the</span> <span class="n">test</span> <span class="n">widget</span> <span class="ow">and</span> <span class="nb">delete</span> <span class="n">it</span>
+<span class="o">*</span> <span class="n">check</span> <span class="n">widget</span> <span class="n">is</span> <span class="ow">not</span> <span class="n">available</span> <span class="n">in</span> <span class="n">widget</span> <span class="n">gallery</span>
+</pre></div>
+
+
+<h2 id="service-types">Service Types</h2>
+<p>FIXME: How do we test this?</p>
+<h2 id="white-list">White List</h2>
+<p>Click White List then carry out the following actions</p>
+<h3 id="access-request-policies">Access request policies</h3>
+<ul>
+<li>click "Manage widget access request policies"</li>
+<li>revoke policies for weather widget</li>
+<li>check Weather widget does not work via the gallery (note it silently fails at present)</li>
+<li>add http://feeds.bbc.co.uk to the whitelist</li>
+<li>check weather widget works via widget gallery</li>
+</ul>
+<h3 id="instantiation">Instantiation</h3>
+<ul>
+<li>go back to the index page (Other - back to main menu)</li>
+<li>click "instantiate a widget"</li>
+<li>select a random widget in "Service Type"</li>
+<li>click submit</li>
+<li>copy URL from returned XML document</li>
+<li>enter URL into browser</li>
+<li>check widget works OK</li>
+</ul>
+<h3 id="reporting">Reporting</h3>
+<p>Thanks for testing. </p>
+<p>Please be sure to report your successes and failures in the developer mailing list.
+Please include:</p>
+<p>Release versions tested: Source/Standalone/WAR
+Server OSs:
+Server and browser separate machines?:
+Servlet Engine:
+Java version:
+Browsers tests:
+Browser versions:
+Tested with Shindig integration?: Yes/No
+Results: All tests passed/I had the following problem(s)</p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2011-2012 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/wookie/trunk/content/docs/developer/release-vote-general.txt
==============================================================================
--- websites/staging/wookie/trunk/content/docs/developer/release-vote-general.txt (added)
+++ websites/staging/wookie/trunk/content/docs/developer/release-vote-general.txt Tue Nov 27 09:54:44 2012
@@ -0,0 +1,34 @@
+To: general@incubator.apache.org
+cc: wookie-dev@incubator.apache.org
+Subject: [VOTE] Release Apache Wookie *.*.*-incubating (General Incubation List)
+
+This is the (*iteration) incubator release for Apache Wookie, with the artifacts being versioned as *.*.*-incubating.
+
+We have already received * IPMC +1 votes (plus an additional * PPMC +1 votes) during the release voting on wookie-dev. (We need * more IPMC vote)
+
+Vote thread:
+http://incubator.markmail.org/search/xxxxxxxxxxxxxxxxxxxxxxxxxxx
+
+Result:
+http://incubator.markmail.org/search/xxxxxxxxxxxxxxxxxxxxxxxxxxx
+
+Svn source tag:
+https://svn.apache.org/repos/asf/incubator/wookie/tags/*.*.*-incubating/
+
+Release notes:
+https://svn.apache.org/repos/asf/incubator/wookie/tags/*.*.*-incubating/RELEASE_NOTES
+
+Release artifacts:
+http://people.apache.org/builds/incubator/wookie/staging-area/*.*.*-incubating
+
+Maven artifacts
+https://repository.apache.org/content/repositories/orgapachewookie-***/
+
+PGP release keys:
+https://svn.apache.org/repos/asf/incubator/wookie/KEYS
+
+Vote open for 72 hours.
+
+[ ] +1 approve
+[ ] +0 no opinion
+[ ] -1 disapprove (and reason why)
\ No newline at end of file
Added: websites/staging/wookie/trunk/content/docs/developer/release-vote.txt
==============================================================================
--- websites/staging/wookie/trunk/content/docs/developer/release-vote.txt (added)
+++ websites/staging/wookie/trunk/content/docs/developer/release-vote.txt Tue Nov 27 09:54:44 2012
@@ -0,0 +1,33 @@
+To: wookie-dev@incubator.apache.org
+Subject: [VOTE] Apache Wookie ${version} Release Candidate
+
+This is the *iteration incubator release for Apache Wookie, with the artifacts being versioned as *.*.*-incubating.
+
+We are requesting a vote via wookie-dev for the release of the artifacts in the first instance found here...
+
+http://people.apache.org/builds/incubator/wookie/*.*.*-incubating/
+
+...as the final *.*.*-incubating release.
+
+PGP release keys (signed using DDED352A):
+
+http://www.apache.org/dist/incubator/wookie/KEYS
+
+Additionally there are 3 sets of maven artifacts, which we hope will help
+others to integrate WOOKIE into their own applications. These are...
+
+1. Wookie itself as a downloadable WAR
+2. The W3C parser
+3. The Java connector framework
+
+These artifacts are now in the staging area found here...
+
+https://repository.apache.org/content/repositories/orgapachewookie-***/
+
+Please take the time to verify the artifacts before casting your vote.
+
+Vote will be open at least 72 hours but until we receive most of the committers votes.
+
+[ ] +1 approve
+[ ] +0 no opinion
+[ ] -1 disapprove (and reason why)
\ No newline at end of file