Author: lmandel
Date: Tue Aug 14 08:03:04 2007
New Revision: 565792
URL: http://svn.apache.org/viewvc?view=rev&rev=565792
Log:
Added initial Woden development process document.
Added:
incubator/woden/Site/src/documentation/content/xdocs/dev/devprocess.xml
Added: incubator/woden/Site/src/documentation/content/xdocs/dev/devprocess.xml
URL:
http://svn.apache.org/viewvc/incubator/woden/Site/src/documentation/content/xdocs/dev/devprocess.xml?view=auto&rev=565792
==============================================================================
--- incubator/woden/Site/src/documentation/content/xdocs/dev/devprocess.xml
(added)
+++ incubator/woden/Site/src/documentation/content/xdocs/dev/devprocess.xml Tue
Aug 14 08:03:04 2007
@@ -0,0 +1,213 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Copyright 2002-2004 The Apache Software Foundation
+
+ Licensed 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.
+-->
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN"
"http://forrest.apache.org/dtd/document-v20.dtd";>
+<document>
+ <header>
+ <title>Woden Decision Making and Development Processes</title>
+ </header>
+ <body>
+ <section>
+ <title>Introduction</title>
+ <p>
+ This document summarizes the Woden decision making and development
processes. It is expected that this
+ document will be useful to
+ </p>
+ <ol>
+ <li>Hold current committers accountable to the established Woden
processes</li>
+ <li>Assist new contributors in getting up-to-speed with the Woden
development processes
+ in order to ensure all Woden contributors are doing things the
Woden way and more
+ generally the Apache way</li>
+ <li>Provide a clear view of the way in which Woden is developed for the
Open Source community</li>
+ </ol>
+ </section>
+ <section>
+ <title>Open Development</title>
+ <p>
+ The development of Apache Woden is being conducted in an open fashion.
This theme should be evident
+ as you read through this guide of the Woden decision making and
development processes.
+ At a high level what Open development means is that the entire
development process of Woden is open to the
+ community. Nothing is kept behind closed doors and information is
readily available via the Woden
+ Web site, mailing list, and wiki.
+ </p>
+ </section>
+ <section>
+ <title>Project Status</title>
+ <p>
+ WS and incubator board reports
+ status file
+ website
+ mailing list
+ </p>
+ </section>
+ <section>
+ <title>Source Code</title>
+ <p>
+ stored in SVN
+ Apache boilerplate link
+ Java coding conventions
+ </p>
+ </section>
+ <section>
+ <title>Testing</title>
+ <p>
+ </p>
+ </section>
+ <section>
+ <title>Bug Tracking and Work Items</title>
+ <p>
+ stored in Jira
+ </p>
+ </section>
+ <section>
+ <title>Project Discussion and Communication</title>
+ <p>
+ mailing list and weekly public status telecons
+ </p>
+ </section>
+ <section>
+ <title>Development Process</title>
+ <p>
+ milestones, plans posted to web site (link), all planned items in jira
+ </p>
+ </section>
+ <section>
+ <title>Release Process</title>
+ <p>
+ The Woden release process involves many steps and checks. To keep
compliant with Apache process requirements
+ of WS and incubator projects it is important that it is followed.
+ </p>
+ <ol>
+ <li>
+ Build and test the current Woden release candidate. The
'buildDist' ANT target will
+ create the binary and source archives (.zip, .tar.gz,
.tar.bz2) and the hash digests
+ (md5, sha1) for each archive file.
+ </li>
+ <li>
+ Sign the binary and source archives, which will create
a .asc signature file for each archive file.<br/>
+ <br/>
+ e.g.<br/>
+ <code>gpg --armor --output
apache-woden-incubating-1.0M7a.zip.asc --detach-sig
apache-woden-incubating-1.0M7a.zip</code><br/>
+ <code>gpg --verify
apache-woden-incubating-1.0M7a.zip.asc apache-woden-incubating-1.0M7a.zip</code>
+ </li>
+ <li>
+ Upload the binary and source archives and their hash
digests and signature files to
+ people.apache.org into some directory path under your
public_html directory so that you can include a
+ link to the files in the [VOTE] request email. Also
upload the KEYS file and release-notes.html
+ from [woden root] and junit-noframes.html from the
[woden root]/build/test-results/html directory.
+ Make sure you chmod the file permissions so others can
read them (e.g. 744).<br/>
+ <br/>
+ e.g.<br/>
+ <code>[jkaputin
home]/public_html/woden/milestones/1.0M7a-incubating</code><br/>
+ ...is accessible at url...<br/>
+ <a
href="http://people.apache.org/~jkaputin/woden/milestones/1.0M7a-incubating/";>http://people.apache.org/~jkaputin/woden/milestones/1.0M7a-incubating/</a><br/>
+ <br/>
+ Note, because Woden is in incubation you must not
upload these files to the Woden project on the
+ file server until the Incubator PMC vote has
passed....so you upload to your own space, then move
+ to Woden space after voting.
+ </li>
+ <li>
+ Check that you can download/unzip the files.<br/>
+ Create hash digests of the downloaded archives and
check them against the downloaded hash files.<br/>
+ <br/>
+ e.g.<br/>
+ <code>$ dir</code><br/>
+ <code>apache-woden-incubating-1.0M7a.zip
apache-woden-incubating-1.0M7a.zip.MD5</code><br/>
+ <code>$ cat
apache-woden-incubating-1.0M7a.zip.MD5</code><br/>
+ <code>3009d6f6fea14b7536c22028944bb03a</code><br/>
+ <code>$ md5sum
apache-woden-incubating-1.0M7a.zip</code><br/>
+ <code>3009d6f6fea14b7536c22028944bb03a
*apache-woden-incubating-1.0M7a.zip</code>
+ </li>
+ <li>
+ Post a vote request email to woden-dev asking devs to
vote on the proposed M7b release.
+ Post the voting results.<br/>
+ When posting a vote request to any mailing list, start
the subject line with the eye-catcher [VOTE].
+ </li>
+ <li>
+ If woden-dev vote successful, post to [EMAIL PROTECTED]
asking the WSPMC to approve a Woden
+ release. Post the voting results.<br/>
+ When posting a vote request to any mailing list, start
the subject line with the eye-catcher [VOTE].
+ </li>
+ <li>
+ If WSPMC vote successful, post to IPMC at [EMAIL
PROTECTED] Be specific about timeframe (usually 3 days).
+ Post the results afterwards. Success criteria is at
least 3 binding IPMC votes (i.e. 3 x +1 from IPMC
+ members). Remember, Dims, Sanjiva and Paul F are IPMC
members as well as WSPMC.<br/>
+ When posting a vote request to any mailing list, start
the subject line with the eye-catcher [VOTE].
+ </li>
+ <li>
+ If IPMC vote successful, move all the release files
from your public_html directory to the Woden
+ file space on people.apache.org.<br/>
+ <br/>
+ <code>cd
/www/people.apache.org/dist/ws/woden</code><br/>
+ <code>cd milestones</code><br/>
+ Create a new directory for the release (e.g.
/1.0M7a-incubating)<br/>
+ Move the release files to this new directory.<br/>
+ Copy the file release-notes.html to a new file called
README.html in this new directory
+ (this will ensure the release notes are displayed after
the list of files, when this
+ directory is accessed via the web).<br/>
+ <br/>
+ e.g.<br/>
+
<code>/www/people.apache.org/dist/ws/woden/milestones/1.0M7a-incubating</code><br/>
+ ...will be accessible via url...<br/>
+
http://people.apache.org/dist/ws/woden/milestones/1.0M7a-incubating/
+ </li>
+ <li>
+ Once again, check that:
+ <ul>
+ <li>the file permissions are set correctly</li>
+ <li>you can download/unzip the files</li>
+ <li>the downloaded hash digests are correct</li>
+ </ul>
+ </li>
+ <li>
+ Update the Woden web site (add the release download to
the Builds page and add a News item
+ announcing the release to the Woden home page).
+ </li>
+ <li>
+ Post a release announcement to woden-dev, [EMAIL
PROTECTED] and [EMAIL PROTECTED]
+ </li>
+ <li>
+ Final step, which Axis2 folks will do, it to upload
Woden release binary jar to a maven
+ repository...I think Dims can upload to ws.zones.
+ </li>
+ </ol>
+ <p>
+ Some example mailing list posts for reference:
+ </p>
+ <p>
+ <a
href="http://mail-archives.apache.org/mod_mbox/ws-woden-dev/200704.mbox/[EMAIL
PROTECTED]">[VOTE] woden-dev and WSPMC</a>
+ </p>
+ <p>
+ <a
href="http://mail-archives.apache.org/mod_mbox/ws-woden-dev/200704.mbox/[EMAIL
PROTECTED]">[RESULT]</a>
+ </p>
+ <p>
+ <a
href="http://mail-archives.apache.org/mod_mbox/ws-woden-dev/200704.mbox/[EMAIL
PROTECTED]">[VOTE] IPMC</a>
+ </p>
+ <p>
+ <a
href="http://mail-archives.apache.org/mod_mbox/ws-woden-dev/200704.mbox/[EMAIL
PROTECTED]">[ANNOUNCE]</a>
+ </p>
+ </section>
+ <section>
+ <title>Connection with W3C WSDL Working Group</title>
+ <p>
+ Close communication as Woden is a reference implementation of WSDL 2.0
+ use and contribute to the test suite
+ problems found in the W3C WSDL test suite or spec should be reported
via the WSDL mailing list [EMAIL PROTECTED] and http://www.w3.org/Bugs/Public/
+ </p>
+ </section>
+
+ </body>
+</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
