THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
The release manager(s) is(are) responsible for targeting fixes into a given version of OpenJPA and may reject changes.
- 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.
- In general only the release manager(s) should target a JIRA issue for a branch which they support.
- An exception to this rule is if the RM has committed changes for their branch and forgot to update the JIRA issue.
- Fixes should not be committed without RM approval. These changes may be reverted by the release manager.
Some general guidelines for release managers
...
The current release managers for the active branches of OpenJPA are :
branch | release manager(s) | Contact Release Manager before committing |
|---|---|---|
0.9.7-r547073 | Srinivasa Segu | Yes |
1.0.x | Michael Dick | Yes |
1.1.x | Patrick Linskey | Yes |
1.2.x | Michael Dick | Yes |
1.3.x | N/A* | |
trunk | N/A* |
* There are no formal releases for these branches.