svn commit: r1767667 - /jackrabbit/site/trunk/src/site/markdown/creating-releases.md

[re...@apache.org]

Author: reschke
Date: Wed Nov  2 13:09:51 2016
New Revision: 1767667

URL: http://svn.apache.org/viewvc?rev=1767667&view=rev
Log:
mention both JCR and OAK Jira pages

Modified:
    jackrabbit/site/trunk/src/site/markdown/creating-releases.md

Modified: jackrabbit/site/trunk/src/site/markdown/creating-releases.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/creating-releases.md?rev=1767667&r1=1767666&r2=1767667&view=diff
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/creating-releases.md (original)
+++ jackrabbit/site/trunk/src/site/markdown/creating-releases.md Wed Nov  2 13:09:51 2016
@@ -58,7 +58,7 @@ Release management tasks
 3. Create a `RELEASE-NOTES.txt` file in the root folder of the project to be released. 
     If such a file already exists, update it for the release. See a previous 
     release notes for examples of what to include. The release note report in Jira is a 
-    useful source of required information: Open the [Jira Oak](https://issues.apache.org/jira/browse/OAK) page, 
+    useful source of required information: Open the [JCR Jira](https://issues.apache.org/jira/browse/JCR) or [OAK Jira](https://issues.apache.org/jira/browse/OAK) page, 
     click on the release, then on the "Release Notes" button on the top right. When done, commit the file.
 4. Build and deploy the release artifacts with Maven. See below for the exact steps.
 5. Do a sanity check that the [staged repository](https://repository.apache.org/index.html#stagingRepositories) on repository.apache.org contains all artifacts (19 projects for Jackrabbit), then close it.