Fixes should be targeted and committed on trunk first. Any other open releases are fair game, but may require approval from a release manager.
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.
The release manager(s) is(are) responsible for targeting fixes into a given version of OpenJPA.
The current release managers for the active branches of OpenJPA are :
branch |
internal release number |
release manager(s) |
Contact Release Manager before committing |
---|---|---|---|
0.9.7-r547073 |
|
Srinivasa Segu |
Yes |
1.0.x |
1.0.5-SNAPSHOT |
Heath Thomann, Donald Woods |
Yes |
1.1.x |
1.1.1-SNAPSHOT |
Patrick Linskey, Abe White |
Yes |
1.2.x |
1.2.3-SNAPSHOT |
Heath Thomann, Donald Woods |
Yes |
1.3.x |
1.3.0-SNAPSHOT |
N/A* |
No |
2.0.x |
2.0.2-SNAPSHOT |
Donald Woods, Heath Thomann |
Yes |
2.1.x |
2.1.1-SNAPSHOT |
Heath Thomann |
Yes |
2.2.x |
2.2.1-SNAPSHOT |
Albert Lee |
Yes |
trunk |
2.3.0-SNAPSHOT |
N/A* |
No |
* There are no formal releases for these branches.
We are using the Apache Hudson server for continuous builds of several releases. Please checkout the Automated Builds page for more details.