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.
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.