You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by re...@apache.org on 2021/09/23 11:32:04 UTC

svn commit: r1893550 - /jackrabbit/site/trunk/src/site/markdown/issue-tracker.md

Author: reschke
Date: Thu Sep 23 11:32:04 2021
New Revision: 1893550

URL: http://svn.apache.org/viewvc?rev=1893550&view=rev
Log:
elaborate on 'fixVersion', and also mention the use of the 'candidate' label)

Modified:
    jackrabbit/site/trunk/src/site/markdown/issue-tracker.md

Modified: jackrabbit/site/trunk/src/site/markdown/issue-tracker.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/issue-tracker.md?rev=1893550&r1=1893549&r2=1893550&view=diff
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/issue-tracker.md (original)
+++ jackrabbit/site/trunk/src/site/markdown/issue-tracker.md Thu Sep 23 11:32:04 2021
@@ -21,6 +21,7 @@ Apache Jackrabbit uses Jira for tracking
 improvements, new features, and other changes.
 
 The issue tracker is available at https://issues.apache.org/jira/browse/JCR
+and https://issues.apache.org/jira/browse/OAK
 and is readable by everyone. A Jira account is needed to create new issues
 and to comment on existing issues. Use the [registration form](https://issues.apache.org/jira/secure/Signup!default.jspa)
 to request an account if you do not already have one.
@@ -46,7 +47,9 @@ included in that release. If the fix is
 the maintenance branches (for backporting, use `svn merge -c _revision_
 ^/jackrabbit/trunk` in the root of the branch) the version numbers of the
 relevant next maintenance releases should also be included in the "Fix
-Version(s)" field.
+Version(s)" field (once the backport is done, not before that!). Note that
+this field is used to generate release notes, thus it needs to be maintained
+properly.
 
 Finally, once a release containing the change has been made, the release
 manager will mark the issue *Closed*, after which the issue can no longer
@@ -54,6 +57,12 @@ be reopened (since the release can obvio
 Potential regressions or other related problems should be tracked in
 separate followup issues.
 
+If a fix has not been backported yet, but should be considered for the next
+release of a maintenance branch, it can be labeled as "candidate_branchname" (or
+"candidate_oak_branchname"). Once the backport for that maintenance branch
+has been done, the label should be removed (or replaced by a label for the next
+older maintenance branch).
+
 
 Issue contents
 --------------