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

[confluence]

Page Edited : openjpa : OpenJPA Release Management OpenJPA Release Management has been edited by Michael Dick (Apr 22, 2009). Change summary: First draft. (View changes) Content: OpenJPA Release Management Or "Where should I put my fix". This is my understanding of the current strategy and may be amended In general bug fixes can be committed in any unreleased branch of OpenJPA. At the moment (April 22, 2009) the unreleased branches are trunk and 1.3.x (because there's no 1.3.0 release). Once a release manager is assigned. The release manager is often (but not always) the same developer who performed the release. The release manager is responsible for targeting fixes into a given version of OpenJPA and may reject changes that they feel have not been sufficiently tested or inject too much risk into a stable stream. 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. 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* * This release is still "open"

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

Unsubscribe or edit your notifications preferences