You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by tu...@apache.org on 2012/06/07 00:39:53 UTC
svn commit: r1347186 - in /incubator/oozie/branches/ap-pages/src/site: ./
apt/
Author: tucu
Date: Wed Jun 6 22:39:52 2012
New Revision: 1347186
URL: http://svn.apache.org/viewvc?rev=1347186&view=rev
Log:
Updating howto contrib/release and doc links for 3.2.0-incubating release
Removed:
incubator/oozie/branches/ap-pages/src/site/apt/QuickStart.apt.vm
incubator/oozie/branches/ap-pages/src/site/apt/mailing_list.apt.vm
incubator/oozie/branches/ap-pages/src/site/apt/quick-start.apt.vm
incubator/oozie/branches/ap-pages/src/site/apt/who_we_are.apt.vm
Modified:
incubator/oozie/branches/ap-pages/src/site/apt/Credits.apt.vm
incubator/oozie/branches/ap-pages/src/site/apt/Downloads.apt.vm
incubator/oozie/branches/ap-pages/src/site/apt/HowToContribute.apt.vm
incubator/oozie/branches/ap-pages/src/site/apt/HowToRelease.apt.vm
incubator/oozie/branches/ap-pages/src/site/site.xml
Modified: incubator/oozie/branches/ap-pages/src/site/apt/Credits.apt.vm
URL: http://svn.apache.org/viewvc/incubator/oozie/branches/ap-pages/src/site/apt/Credits.apt.vm?rev=1347186&r1=1347185&r2=1347186&view=diff
==============================================================================
--- incubator/oozie/branches/ap-pages/src/site/apt/Credits.apt.vm (original)
+++ incubator/oozie/branches/ap-pages/src/site/apt/Credits.apt.vm Wed Jun 6 22:39:52 2012
@@ -36,6 +36,10 @@ Apache Oozie(TM) Credits
*----------------------+-----------------------+----------------------------------------------------------------------+
|Chao Wang |brookwc |IBM Corporation |
*----------------------+-----------------------+----------------------------------------------------------------------+
+|Virag Kothari |virag |Yahoo Inc. |
+*----------------------+-----------------------+----------------------------------------------------------------------+
+|Harsh Chouraria |qwertymaniac |Cloudera Inc.
+*----------------------+-----------------------+----------------------------------------------------------------------+
* Contributors
@@ -49,8 +53,6 @@ Apache Oozie(TM) Credits
*----------------------+-----------------------+----------------------------------------------------------------------+
|Alan Gates |gates |Hortonworks Inc. |
*----------------------+-----------------------+----------------------------------------------------------------------+
-|Christopher Douglas |cdouglas |Yahoo Inc. |
-*----------------------+-----------------------+----------------------------------------------------------------------+
-|Devaraj Das |ddas |Hortonworks Inc. |
+|Christopher Douglas |cdouglas |- |
*----------------------+-----------------------+----------------------------------------------------------------------+
Modified: incubator/oozie/branches/ap-pages/src/site/apt/Downloads.apt.vm
URL: http://svn.apache.org/viewvc/incubator/oozie/branches/ap-pages/src/site/apt/Downloads.apt.vm?rev=1347186&r1=1347185&r2=1347186&view=diff
==============================================================================
--- incubator/oozie/branches/ap-pages/src/site/apt/Downloads.apt.vm (original)
+++ incubator/oozie/branches/ap-pages/src/site/apt/Downloads.apt.vm Wed Jun 6 22:39:52 2012
@@ -17,9 +17,9 @@
Apache Oozie(TM) Downloads
- Oozie Apache released version can be downloaded from this link:
+ Oozie Apache released versions can be downloaded from this link:
- {{{http://www.apache.org/dyn/closer.cgi/incubator/oozie/}Oozie 3.1.3 Download}}
+ {{{http://www.apache.org/dyn/closer.cgi/incubator/oozie/}Apache Oozie Download}}
- Older releases can be accessed through github site at : {{{http://github.com/yahoo/oozie/downloads}Github Downloads}}
+ Older releases can be accessed through github site at : {{{http://github.com/yahoo/oozie/downloads}Yahoo Oozie Downloads}}
Modified: incubator/oozie/branches/ap-pages/src/site/apt/HowToContribute.apt.vm
URL: http://svn.apache.org/viewvc/incubator/oozie/branches/ap-pages/src/site/apt/HowToContribute.apt.vm?rev=1347186&r1=1347185&r2=1347186&view=diff
==============================================================================
--- incubator/oozie/branches/ap-pages/src/site/apt/HowToContribute.apt.vm (original)
+++ incubator/oozie/branches/ap-pages/src/site/apt/HowToContribute.apt.vm Wed Jun 6 22:39:52 2012
@@ -30,7 +30,7 @@ Apache Oozie(TM) How to Contribute
* (Optional) An IDE (ie. Eclipse, IntelliJ, Netbeans can be easily used with the IDEs Maven support).
- * To be online for the first build to download required plugins and dependencies.
+ * Be online for the first build to download required plugins and dependencies.
* Getting the Source
@@ -50,42 +50,41 @@ Apache Oozie(TM) How to Contribute
First create an issue in {{{./IssueTracking.html}Oozie Issue Tracking System}} describing the bug,
improvement, new feature, task; and discuss if appropiate. It is important that the subject of
- the issue to be descriptive of the issue, and consize, as it will be used for the CHANGES log.
+ the issue to be descriptive of the issue, and consize, as it will be used for the RELEASE LOG.
All discussions should be done in the Issue Tracking System to make easier for developers to
follow or come back in the future.
Oozie development follows a Review Then Commit model.
Work on the issue in your local development environment and when you think it is ready for review
- or integration submit the patch for a code review request using
- {{{http://reviews.apache.org}Apache Code Review System}}.
+ or integration upload your patch to the JIRA issue (remember to grant license to Apache) and change
+ the status of the JIRA to 'Patch Available'.
Refine the patch based on the review discussions.
- <<Important facts about the Code Review system>>:
+ Once your patch has been +1ed by Oozie committers (according to the project bylaws) the patch
+ can be committed to the Version Control system. If you are a committer, you can commit it
+ yourself. If you are not a committer, one of the committers that +1ed the patch will commit it
+ on your behalf.
+
+ If required, backports for releases branches should follow. If the backports are trivial there
+ is no need for a new review.
+
+ The corresponding issue in the Issue Tracking and in the Code Review systems must be resolved as
+ 'fixed' by the committer once the patch has been committed to all relevant branches.
+
+ <<IMPORTANT:>> Do not 'Close' the issue, resolve it as 'Fixed'. The issue will be closed by
+ the release mananger of the of the target release branch at release time.
+
+ If the reviewers consider that it will easier to review the patch to
+ {{{http://reviews.apache.org}Apache Code Review System}}, he/she may upload the patch to Apache
+ Code Review System, or ask the contributor of the patch to do so. Once the review is complete
+ in Apache Code Review System, the contributor must upload the final patch to the Apache JIRA
+ where it will be +1.
+
+* Patches General Guidelines
- * The Code Review system is integrated with the Issue Tracking system (all review discussions
- are logged in the Issue tracking system). For this you must enter the issue ID in the review
- request.
-
- * The Code Review system is shared with other Apache projects, you must enter <<oozie>> as the
- group for the review request.
-
- * The Code Review system only accept patches generated with <<svn diff>> syntax
- (<<git diff --no-prefix>> syntax is not accepted. If you work using Apache Git repository,
- you'll have to apply the patch to an SVN checkout and then generate the SVN patch from there).
-
- Once your patch has been +1ed by Oozie committers (according to the project bylaws) the patch
- can be committed to the Version Control system. If you are a committer, you can commit it
- yourself. If you are not a committer, one of the committers that +1ed the patch will commit it
- on your behalf.
-
- The corresponding issue in the Issue Tracking and in the Code Review systems must be closed as
- 'fixed'by the committer once the patch has been committed to all relevant branches.
-
- * Patches General Guidelines
-
- ** Coding Conventions
+** Coding Conventions
Oozie uses {{{http://java.sun.com/docs/codeconv/CodeConventions.pdf}Java standard coding conventions}}
with the following changes:
@@ -109,6 +108,8 @@ Apache Oozie(TM) How to Contribute
* Don't reformat code that is not part of the patch.
+ * else/catch/finally start on a new line.
+
** Test Cases
All patches should include test cases whenever possible. Test cases should have as much coverage
@@ -118,7 +119,7 @@ Apache Oozie(TM) How to Contribute
If the patch is adding/modifying functionality that is user facing, it must include documentation.
-** Changes Log File
+** Release Log File
- The Changes Log file must be edited by the committer committing the patch (the patch must not
- include changes to the Changes Log file). This is to avoid unnecessary conflicts.
+ The Release Log file must be edited by the committer committing the patch (the patch must not
+ include changes to the Release Log file). This is to avoid unnecessary conflicts.
Modified: incubator/oozie/branches/ap-pages/src/site/apt/HowToRelease.apt.vm
URL: http://svn.apache.org/viewvc/incubator/oozie/branches/ap-pages/src/site/apt/HowToRelease.apt.vm?rev=1347186&r1=1347185&r2=1347186&view=diff
==============================================================================
--- incubator/oozie/branches/ap-pages/src/site/apt/HowToRelease.apt.vm (original)
+++ incubator/oozie/branches/ap-pages/src/site/apt/HowToRelease.apt.vm Wed Jun 6 22:39:52 2012
@@ -17,13 +17,15 @@
Apache Oozie(TM) How to Release
- This page is to document the release procedure for Oozie. Oozie is currently a Apache incubator project.
+ This page is to document the release procedure for Oozie. Oozie is currently
+ a Apache incubator project.
Its release process is still <<<work in progress>>>.
* Preparation
- [[1]] A committer proposes a release and a release manager is chosen by the committers (normally the
+ [[1]] A committer proposes a release and a release manager is chosen by the
+ committers (normally the
committer proposing the release would be the release manager).
[[1]] Agree on the initial scope for the release and update JIRAs accordingly.
@@ -32,14 +34,17 @@ Apache Oozie(TM) How to Release
* Create the Release Branch
- A new release branch is created only for for major (X.0.0) and minor (X.Y.0) releases but not for patches (X.Y.Z).
- A patch is an update to an existing branch created for X.Y.0. A patch release must be tagged.
+ A new release branch is created only for for major (X.0.0) and minor (X.Y.0)
+ releases but not for patches (X.Y.Z). A patch is an update to an existing
+ branch created for X.Y.0. A patch release must be tagged.
[[1]] Send email to oozie-dev@incubator.apache.org to notify that
- [[A]] A new branch is about to be created from trunk, from a major branch or from a minor branch.
+ [[A]] A new branch is about to be created from trunk, from a major branch
+ or from a minor branch.
- [[A]] Request to hold off any commits from the corresponding branch until further email.
+ [[A]] Request to hold off any commits from the corresponding branch until
+ further email.
[[1]] Create a branch for the release.
@@ -50,24 +55,28 @@ svn copy https://svn.apache.org/repos/as
https://svn.apache.org/repos/asf/incubator/oozie/branches/branch-X.Y -m "Branching for X.Y releases"
-----------------------------------------------------------------------------
- [[1]] Update the original branch ticking the corresponding major or minor version in all POMs
+ [[1]] Update the original branch ticking the corresponding major or minor
+ version in all POMs
(use the Maven versions plugin).
- [[1]] Send email to oozie-dev@incubator.apache.org to notify that the release branch has been created and that
- commits can resume.
+ [[1]] Send email to oozie-dev@incubator.apache.org to notify that the
+ release branch has been created and that commits can resume.
[]
* Work on the Release Branch
- [[1]] Work on existing JIRAs and new ones until the release manager feels that the branch is ready for a release.
+ [[1]] Work on existing JIRAs and new ones until the release manager feels that
+ the branch is ready for a release.
- [[2]] As a general rule, JIRAs must be committed first to trunk and the backported to the branch. Only for cases
- where the JIRAs does not apply to trunk the JIRA should be only committed to the branch.
+ [[2]] As a general rule, JIRAs must be committed first to trunk and the
+ backported to the branch. Only for cases where the JIRAs does not apply to
+ trunk the JIRA should be only committed to the branch.
* Updating Release Branch
- These steps are required for all the releases (such as major, minor, and patches).
+ These steps are required for all the releases (such as major, minor, and
+ patches).
[[1]] Check out the branch with:
@@ -75,14 +84,17 @@ https://svn.apache.org/repos/asf/incubat
svn co https://svn.apache.org/repos/asf/incubator/oozie/branches/branch-X.Y
-----------------------------------------------------------------------------
- [[1]] Create <rat> report to verify all files have the corresponding Apache License header.
- The generated report will be used later. (TBD: How to combine rat report generated for each sub-projects?)
+ [[1]] Create <rat> report to verify all files have the corresponding Apache
+ License header.
+ The generated report will be used later. (TBD: How to combine rat report
+ generated for each sub-projects?)
-----------------------------------------------------------------------------
mvn apache-rat:check
-----------------------------------------------------------------------------
- [[1]] Tag the release candidate, where R is the iteration number for this release candidate, starting with 0:
+ [[1]] Tag the release candidate, where R is the iteration number for this
+ release candidate, starting with 0:
-----------------------------------------------------------------------------
svn copy https://svn.apache.org/repos/asf/incubator/oozie/branches/branch-X.Y \
@@ -107,8 +119,8 @@ https://svn.apache.org/repos/asf/incubat
[[1]] If you do not have a gpg key pair, do the following steps:
- [[A]] Generating key pair using the following command. You can simply accept all default settings and give
- your name, email and Passphase.
+ [[A]] Generating key pair using the following command. You can simply
+ accept all default settings and give your name, email and Passphase.
-----------------------------------------------------------------------------
gpg --gen-key
@@ -120,8 +132,8 @@ https://svn.apache.org/repos/asf/incubat
gpg --armor --output pubkey.txt --export 'Your Name'
-----------------------------------------------------------------------------
- [[A]] Open pubkey.txt, copy the full text and append it to the following files by pasting, then commit these
- changes:
+ [[A]] Open pubkey.txt, copy the full text and append it to the following
+ files by pasting, then commit these changes:
-----------------------------------------------------------------------------
https://svn.apache.org/repos/asf/incubator/oozie/branches/branch-X.Y.Z/KEYS
@@ -140,7 +152,8 @@ https://svn.apache.org/repos/asf/incubat
gpg --export-secret-key -a "Your Name" > private.key
-----------------------------------------------------------------------------
- [[1]] Sign the release (see Step-By-Step Guide to Mirroring Releases for more information).
+ [[1]] Sign the release (see Step-By-Step Guide to Mirroring Releases for
+ more information).
-----------------------------------------------------------------------------
gpg --armor --output oozie-X.Y.Z-incubating.tar.gz.asc --detach-sig oozie-X.Y.Z-incubating.tar.gz
@@ -153,31 +166,41 @@ https://svn.apache.org/repos/asf/incubat
gpg --verify oozie-X.Y.Z-incubating.tar.gz.asc oozie-X.Y.Z-incubating.tar.gz
-----------------------------------------------------------------------------
- [[1]] Copy release files to a public place (usually into public_html in your home directory):
+ [[1]] Copy release files to a public place (usually into public_html in your
+ home directory):
-----------------------------------------------------------------------------
ssh people.apache.org mkdir public_html/oozie-X.Y.Z-incubating-candidate-0
scp -p oozie-X.Y.Z-incubating.tar.gz* people.apache.org:public_html/oozie-X.Y.Z-incubating-candidate-0
- cd ..
scp release_log.txt people.apache.org:public_html/oozie-X.Y.Z-incubating-candidate-0
scp rat_report people.apache.org:public_html/oozie-X.Y.Z-incubating-candidate-0
-----------------------------------------------------------------------------
- NOTE: The rat_report is the report generated in the Updating Release Branch section above.
+ NOTE: The rat_report is the report generated in the Updating Release Branch
+ section above.
- [[1]] Call a release vote for the Podling PMC (PPMC). This vote must receive a minimum of 3 PPMC members +1s, and more +1s than -1s. The email should be sent to oozie-user@incubator.apache.org. The mail should:
-
- [[A]] Have a subject line "[VOTE] Release Oozie X.Y.Z-incubating (candidate a)" where X.Y.Z is the version number and a is the candidate number for this release.
+ [[1]] Call a release vote for the Oozie Podling PMC (PPMC). Per Apache
+ Incubator rules, this vote is non-binding, but it help us catching issues
+ with the release candidate before calling for an Incubator IPMC vote and to
+ practice how things will be as a top level project. This vote must receive a
+ minimum of 3 Oozie committers +1s, and more +1s than -1s. The email should
+ be sent to oozie-dev@incubator.apache.org. The mail should:
+
+ [[A]] Have a subject line "[VOTE] Release Oozie X.Y.Z-incubating
+ (candidate a)" where X.Y.Z is the version number and a is the candidate
+ number for this release.
[[A]] State what are new in this release.
[[A]] Tell where the keys used to sign the release can be found.
- [[A]] State where the release, md5 signature, gpg signature, and rat report can be found.
+ [[A]] State where the release, md5 signature, gpg signature, and rat
+ report can be found.
[[A]] Request that users and developers download it, test it, and vote.
- [[A]] State when the vote closes. The vote must remain open for at least 72 hours. It can be longer at your discretion (e.g. around major holidays).\
+ [[A]] State when the vote closes. The vote must remain open for at least
+ 72 hours. It can be longer at your discretion (e.g. around major holidays).\
Here is a sample email:
-----------------------------------------------------------------------------
@@ -185,22 +208,28 @@ https://svn.apache.org/repos/asf/incubat
Hi,
- I have created a candidate build for Oozie X.Y.Z-incubating. This is the first release of Oozie from Apache Incuabtion.
+ I have created a candidate build for Oozie X.Y.Z-incubating. This
+ is the first release of Oozie from Apache Incuabtion.
- Keys used to sign the release are available at http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
+ Keys used to sign the release are available at
+ http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.
Please download, test, and try it out:
http://people.apache.org/~you/oozie-X.Y.Z-incubating-candidate-0
- The release, md5 signature, gpg signature, and rat report can all be found at the above address.
+ The release, md5 signature, gpg signature, and rat report can all
+ be found at the above address.
Should we release this? Vote closes on <DATE>.
Me
-----------------------------------------------------------------------------
- [[1]] If the PPMC approves the release, call an Incubator PMC (IPMC) vote. This vote must receive a minimum of 3 IPMC member +1s, and more +1s than -1s. The email sent should look similar to PPMC.
+ [[1]] If Oozie PPMC approves the release, call an Incubator PMC (IPMC) vote.
+ This vote must receive a minimum of 3 IPMC member +1s, and more +1s than -1s.
+ The email should be sent to the general@incubator.apache.org alias, it should
+ be the original email prefixed with the Oozie PPMC tally.
[]
* Publish
@@ -214,7 +243,8 @@ https://svn.apache.org/repos/asf/incubat
https://svn.apache.org/repos/asf/incubator-oozie/tags/release-X.Y.Z -m "Oozie X.Y.Z release."
-----------------------------------------------------------------------------
- [[1]] Copy the release files to the distribution directory and make them writable by the oozie group.
+ [[1]] Copy the release files to the distribution directory and make them
+ writable by the oozie group.
-----------------------------------------------------------------------------
ssh people.apache.org
@@ -234,7 +264,8 @@ https://svn.apache.org/repos/asf/incubat
[[1]] Wait until you see your changes reflected on the Apache web site.
- [[1]] Send announcements to the user and developer lists as well as (announce@haoop.apache.org) once the site changes are visible.
+ [[1]] Send announcements to the user and developer lists as well as
+ (announce@haoop.apache.org) once the site changes are visible.
-----------------------------------------------------------------------------
The Oozie team is happy to announce the release of Oozie X.Y.Z.
@@ -242,7 +273,8 @@ https://svn.apache.org/repos/asf/incubat
Apache Oozie provides a workflow management and scheduling for Hadoop jobs.
More details about Oozie can be found at http://incubator.apache.org/oozie.
- The highlights of this release are ... The details of the release can be found at http://incubator.apache.org/oozie/releases.html.
+ The highlights of this release are ... The details of the release can be
+ found at http://incubator.apache.org/oozie/releases.html.
-----------------------------------------------------------------------------
[]
[[1]] In JIRA, mark the release as released.
@@ -255,9 +287,12 @@ https://svn.apache.org/repos/asf/incubat
[[A]] Select Release for the version you have released.
- [[A]] If a description has not yet been added for the version you are releasing, select Edit Details and give a brief description of the release.
+ [[A]] If a description has not yet been added for the version you are
+ releasing, select Edit Details and give a brief description of the release.
- [[A]] If the next version does not exist (that is, if you are releasing version X.Y, if version X.Y+1 does not yet exist) create it using the Add Version box at the top of the page.
+ [[A]] If the next version does not exist (that is, if you are releasing
+ version X.Y, if version X.Y+1 does not yet exist) create it using the
+ Add Version box at the top of the page.
[[1]] In JIRA, mark the issues resolved in this release as closed.
@@ -271,7 +306,8 @@ https://svn.apache.org/repos/asf/incubat
[[A]] Click "Search" button
- [[A]] In the next screen, further select fix For select the version you are releasing.
+ [[A]] In the next screen, further select fix For select the version you
+ are releasing.
[[A]] Click on the "Search" button
@@ -283,9 +319,12 @@ https://svn.apache.org/repos/asf/incubat
[[A]] Select "Close Issue" radio button and click on "Next"
- [[A]] Uncheck the box near the bottom at says "Send mail for this update" lest you spam every Oozie developer with a message for every bug resolved in this release. Click "Next".
+ [[A]] Uncheck the box near the bottom at says "Send mail for this update"
+ lest you spam every Oozie developer with a message for every bug resolved
+ in this release. Click "Next".
- [[A]] Click "Confirm". Don't worry if it gives you a HTTP 500 error, it still does the transitions.
+ [[A]] Click "Confirm". Don't worry if it gives you a HTTP 500 error, it
+ still does the transitions.
[]
Modified: incubator/oozie/branches/ap-pages/src/site/site.xml
URL: http://svn.apache.org/viewvc/incubator/oozie/branches/ap-pages/src/site/site.xml?rev=1347186&r1=1347185&r2=1347186&view=diff
==============================================================================
--- incubator/oozie/branches/ap-pages/src/site/site.xml (original)
+++ incubator/oozie/branches/ap-pages/src/site/site.xml Wed Jun 6 22:39:52 2012
@@ -14,49 +14,50 @@
-->
<project name="Apache Oozie">
- <version position="right"/>
+ <version position="right"/>
- <bannerLeft>
- <name> </name>
- </bannerLeft>
-
- <skin>
- <groupId>org.apache.maven.skins</groupId>
- <artifactId>maven-stylus-skin</artifactId>
- <version>1.3</version>
- </skin>
-
- <body>
- <links>
- <item name="ASF" href="http://www.apache.org/"/>
- </links>
- <breadcrumbs>
- <item name="Apache Oozie" href="index.html"/>
- </breadcrumbs>
-
- <menu name="Project">
- <item name="Home" href="./index.html"/>
- <item name="Downloads" href="./Downloads.html"/>
- <item name="Credits" href="./Credits.html"/>
- <item name="Mailing Lists" href="./MailingLists.html"/>
- <item name="Issue Tracking" href="./IssueTracking.html"/>
- <item name="IRC Channel" href="./IRCChannel.html"/>
- </menu>
-
- <menu name="Developers">
- <item name="Version Control" href="./VersionControl.html"/>
- <item name="How To Contribute" href="./HowToContribute.html"/>
- <item name="How to Release" href="HowToRelease.html"/>
- </menu>
-
- <menu name="Documentation">
- <item name="3.1.3" href="./docs/3.1.3/docs/index.html"/>
- <item name="Quick start" href="./QuickStart.html"/>
- <item name="Overview" href="./overview.html"/>
- <item name="MapReduce Cookbook" href="./map-reduce-cookbook.html"/>
- <item name="Pig Cookbook" href="./pig-cookbook.html"/>
- </menu>
+ <bannerLeft>
+ <name> </name>
+ </bannerLeft>
+
+ <skin>
+ <groupId>org.apache.maven.skins</groupId>
+ <artifactId>maven-stylus-skin</artifactId>
+ <version>1.3</version>
+ </skin>
+
+ <body>
+ <links>
+ <item name="ASF" href="http://www.apache.org/"/>
+ </links>
+ <breadcrumbs>
+ <item name="Apache Oozie" href="index.html"/>
+ </breadcrumbs>
+
+ <menu name="Project">
+ <item name="Home" href="./index.html"/>
+ <item name="Downloads" href="./Downloads.html"/>
+ <item name="Credits" href="./Credits.html"/>
+ <item name="Mailing Lists" href="./MailingLists.html"/>
+ <item name="Issue Tracking" href="./IssueTracking.html"/>
+ <item name="IRC Channel" href="./IRCChannel.html"/>
+ </menu>
+
+ <menu name="Developers">
+ <item name="Version Control" href="./VersionControl.html"/>
+ <item name="How To Contribute" href="./HowToContribute.html"/>
+ <item name="How to Release" href="HowToRelease.html"/>
+ </menu>
+
+ <menu name="Documentation">
+ <item name="3.2.0-incubating" href="./docs/3.2.0-incubating/docs/index.html"/>
+ <item name="Quick start" href="./docs/3.2.0-incubating/docs/QuickStart.html"/>
+ <item name="Overview" href="./overview.html"/>
+ <item name="MapReduce Cookbook" href="./map-reduce-cookbook.html"/>
+ <item name="Pig Cookbook" href="./pig-cookbook.html"/>
+ <item name="Older releases" href="./docs"/>
+ </menu>
- </body>
+ </body>
</project>