[CONF] OpenJPA: OpenJPA Release Management (page edited)

[confluence]

Page Edited : openjpa : OpenJPA Release Management OpenJPA Release Management has been edited by Michael Dick (Apr 23, 2009). (View changes) Content: OpenJPA Release Management Where should I put my fix? Fixes should be targeted and committed on trunk first. Any other open releases are fair game, but may require approval from a release manager. Regarding Release Managers 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 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. Some general guidelines for release managers 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. Issues may not apply to every release, so the previous guideline may not always apply. Release Managers for active branches. The current release managers for the active branches of OpenJPA are : branch release manager(s) 0.9.7-r547073 Srinivasa Segu 1.0.x Michael Dick 1.1.x Patrick Linskey Abe White 1.2.x Michael Dick 1.3.x N/A* trunk N/A* * There are no formal releases for these branches.

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences