openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r879197 - in /websites/staging/openjpa/trunk/content: ./ jpa-specification-development.html
Date Fri, 20 Sep 2013 18:17:25 GMT
Author: buildbot
Date: Fri Sep 20 18:17:25 2013
New Revision: 879197

Staging update by buildbot for openjpa

    websites/staging/openjpa/trunk/content/   (props changed)

Propchange: websites/staging/openjpa/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Fri Sep 20 18:17:25 2013
@@ -1 +1 @@

Modified: websites/staging/openjpa/trunk/content/jpa-specification-development.html
--- websites/staging/openjpa/trunk/content/jpa-specification-development.html (original)
+++ websites/staging/openjpa/trunk/content/jpa-specification-development.html Fri Sep 20 18:17:25
@@ -22,7 +22,7 @@ limitations under the License.
         <!-- <link href="" rel="stylesheet"
type="text/css"/> -->
         <link href="./css/type-settings.css" rel="stylesheet" type="text/css"/>
         <LINK rel="schema.DC" href="">
-        <META name="Description" content="Apache OpenJPA -- Release Management" />
+        <META name="Description" content="Apache OpenJPA -- JPA Specification Development"
         <META name="Keywords" content="Apache OpenJPA, JPA, JPA 1.0, JSR-220, JPA2, JPA
2.0, JSR-317, " />
         <META name="Owner" content="" />
         <META name="Robots" content="index, follow" />
@@ -68,7 +68,7 @@ limitations under the License.
                             <div class="bottom_red_bar">
                                 <div id="site-breadcrumbs">
                                     <!-- Breadcrumbs --
-                                    <a href="/">Home</a>&nbsp;&raquo&nbsp;<a
href="/jpa-specification-development.html">Release Management</a>
+                                    <a href="/">Home</a>&nbsp;&raquo&nbsp;<a
href="/jpa-specification-development.html">JPA Specification Development</a>
                                      -- Breadcrumbs -->
@@ -145,16 +145,17 @@ limitations under the License.
                                         <td valign="top" width="100%" style="overflow:hidden;">
                                             <div class="wiki-content">
-                                                <p><a name="ReleaseManagement-ReleaseManagement"></a></p>
-<h1 id="release-management">Release Management</h1>
+                                                <p><a name="JPASpecifcationDevelopment"></a></p>
+<h1 id="jpa-specification-development">JPA Specification Development</h1>
+<p>This page will be used to track the development of major JPA Specification levels.
+management of OpenJPA releases (ie. 1.x, 2.x, etc) can be found <A href="release-management.html"
title="Release Management">here</A>.</p>
-<LI><A href="2.1-roadmap.html" title="2.1 Roadmap">2.1 Roadmap</A></LI>
-<LI><A href="apache-nexus-release-process-(1.2.x-2.1.x).html" title="Apache Nexus
Release Process (1.2.x-2.1.x)">Apache Nexus Release Process (1.2.x-2.1.x)</A>
+<LI><A href="jpa-2.1-roadmap.html" title="JPA 2.1 Roadmap">JPA 2.1 Roadmap</A>
- <LI><A href="release-setup.html" title="Release Setup">Release Setup</A></LI>
- <LI><A href="release-artifact-locations.html" title="Release Artifact Locations">Release
Artifact Locations</A></LI>
- </UL></LI>
-<LI><A href="publishing-serp-to-maven-central-repository.html" title="Publishing
Serp to Maven Central Repository">Publishing Serp to Maven Central Repository</A></LI>
+ <LI><A href="jpa-2.1-development-process.html" title="JPA 2.1 Development Process">JPA
2.1 Development Process</A></LI>
+ <LI><A href="jpa-2.1-tasks.html" title="JPA 2.1 Tasks">JPA 2.1 Tasks</A></LI>
+ <LI><A href="jpa-2.1-test-coverage.html" title="JPA 2.1 Test Coverage">JPA 2.1
Test Coverage</A></LI>
 <LI><A href="jpa-2.0-roadmap.html" title="JPA 2.0 Roadmap">JPA 2.0 Roadmap</A>
  <LI><A href="jpa-2.0-development-process.html" title="JPA 2.0 Development Process">JPA
2.0 Development Process</A></LI>
@@ -171,64 +172,7 @@ limitations under the License.
  <LI><A href="openjpa-2.0.0-milestone-3.html" title="OpenJPA 2.0.0 Milestone 3">OpenJPA
2.0.0 Milestone 3</A></LI>
  <LI><A href="openjpa-2.0.1.html" title="OpenJPA 2.0.1">OpenJPA 2.0.1</A></LI>
-<LI><A href="releasing-openjpa-1.0.x-or-1.1.x-(old-scp-steps).html" title="Releasing
OpenJPA 1.0.x or 1.1.x (Old SCP Steps)">Releasing OpenJPA 1.0.x or 1.1.x (Old SCP Steps)</A>
- <UL><LI><A href="openjpa-release-policy.html" title="OpenJPA Release Policy">OpenJPA
Release Policy</A></LI>
- </UL></LI>
-<LI><A href="releasing-openjpa-1.2.x-(old-scp-steps).html" title="Releasing OpenJPA
1.2.x (Old SCP Steps)">Releasing OpenJPA 1.2.x (Old SCP Steps)</A>
- <UL>
- <LI><A href="recovering-from-a-vetoed-release.html" title="Recovering from a vetoed
release">Recovering from a vetoed release</A></LI>
- <LI><A href="running-openjpa-examples.html" title="Running OpenJPA Examples">Running
OpenJPA Examples</A></LI>
- <LI><A href="update-release-text-files.html" title="Update release text files">Update
release text files</A></LI>
- <LI><A href="verifying-release-signatures.html" title="Verifying release signatures">Verifying
release signatures</A></LI>
- </UL></LI>
-<p><a name="ReleaseManagement-WhereshouldIputmyfix?"></a></p>
-<h2 id="where-should-i-put-my-fix">Where should I put my fix?</h2>
-<p>Fixes should be targeted and committed on trunk first. Any other open
-releases are fair game, but may require approval from a release manager. </p>
-<p><a name="ReleaseManagement-RegardingReleaseManagers"></a></p>
-<h2 id="regarding-release-managers">Regarding Release Managers</h2>
-<p>Once a formal release of OpenJPA has been approved, a release manager is assigned.
The release manager is often (but not always) the same developer who performed the release.
This release manager role is intended to be a long term branch maintainer who looks after
the stability of a formal release. </p>
-<p>The release manager(s) is(are) responsible for targeting fixes into a given version
of OpenJPA.</p>
-<li>Release managers may indicate this by targeting a JIRA issue for their branch or
may issue a blanket statement that any fix will be accepted. </li>
-<li>In general only the release manager(s) should target a JIRA issue for a branch
which they support. <ul>
-<li>An exception to this rule is if the RM has committed changes for their branch and
forgot to update the JIRA issue. </li>
-<li>Fixes should not be committed without RM approval. These changes may be reverted
by the release manager. </li>
-<p><a name="ReleaseManagement-Somegeneralguidelinesforreleasemanagers"></a></p>
-<h2 id="some-general-guidelines-for-release-managers">Some general guidelines for release
-<li>Fixes which are committed to an earlier release should also be present
-"up-stream". Ie a fix for 1.0.x should also appear in 1.2.x. </li>
-<li>Issues may not apply to every release, so the previous guideline may not
-always apply.</li>
-<p><a name="ReleaseManagement-ReleaseManagersforactivebranches."></a></p>
-<h2 id="release-managers-for-active-branches">Release Managers for active branches.</h2>
-<p>The current release managers for the active branches of OpenJPA are :</p>
-<table border="0.5">
-<tr bgcolor="lightyellow"><th> branch </th><th> internal release
number </th><th> release manager(s)</th><th> Contact
-Release Manager before committing </th></tr>
-<tr><td class="border"> 0.9.7-r547073 </td><td class="border"> </td><td
class="border"> Srinivasa Segu </td><td class="border"> Yes </td></tr>
-<tr><td class="border"> 1.0.x </td><td class="border"> 1.0.5-SNAPSHOT
</td><td class="border"> Heath Thomann, Donald Woods </td><td class="border">
Yes </td></tr>
-<tr><td class="border"> 1.1.x </td><td class="border"> 1.1.1-SNAPSHOT
</td><td class="border"> Patrick Linskey, Abe White </td><td class="border">
Yes </td></tr>
-<tr><td class="border"> 1.2.x </td><td class="border"> 1.2.3-SNAPSHOT
</td><td class="border"> Heath Thomann, Donald Woods </td><td class="border">
 Yes </td></tr>
-<tr><td class="border"> 1.3.x </td><td class="border"> 1.3.0-SNAPSHOT
</td><td class="border"> N/A (*) </td><td class="border"> No </td></tr>
-<tr><td class="border"> 2.0.x </td><td class="border"> 2.0.2-SNAPSHOT
</td><td class="border"> Donald Woods, Heath Thomann </td><td class="border">
Yes </td></tr>
-<tr><td class="border"> 2.1.x </td><td class="border"> 2.1.1-SNAPSHOT
</td><td class="border"> Heath Thomann </td><td class="border"> Yes
-<tr><td class="border"> 2.2.x </td><td class="border"> 2.2.2-SNAPSHOT
</td><td class="border"> Heath Thomann, Albert Lee </td><td class="border">
Yes </td></tr>
-<tr><td class="border"> 2.2.1.x </td><td class="border">
</td><td class="border"> Heath Thomann, Albert Lee </td><td class="border">
Yes </td></tr>
-<tr><td class="border"> trunk </td><td class="border"> 2.3.0-SNAPSHOT
</td><td class="border"> N/A (*)</td><td class="border"> No </td></tr>
-<p><strong>*</strong> There are no formal releases for these branches.</p>
-<p><a name="ReleaseManagement-ContinuousBuilds"></a></p>
-<h2 id="continuous-builds">Continuous Builds</h2>
-<p>We are using the Apache Hudson server for continuous builds of several releases.
 Please checkout the <a href="automated-builds.html">Automated Builds</a> page
for more details.</p>

View raw message