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 2017/01/24 10:51:26 UTC
svn commit: r1780058 -
/jackrabbit/site/trunk/src/site/markdown/creating-releases.md
Author: reschke
Date: Tue Jan 24 10:51:26 2017
New Revision: 1780058
URL: http://svn.apache.org/viewvc?rev=1780058&view=rev
Log:
add a reminder about updating API docs
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=1780058&r1=1780057&r2=1780058&view=diff
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/creating-releases.md (original)
+++ jackrabbit/site/trunk/src/site/markdown/creating-releases.md Tue Jan 24 10:51:26 2017
@@ -92,6 +92,7 @@ Release management tasks
2. downloads.md (while doing so please a) remove obsoleted entries, and b) move new entries for Jackrabbit and/or Oak to the top)
13. Send the release announcement once the web site and download mirrors have been synced. Please note the announce mails needs to be sent from an @apache.org address.
14. If the release was a Jackrabbit release used in Oak, make sure to also update the dependency in oak-parent/pom.xml (example: [OAK-4743](https://issues.apache.org/jira/browse/OAK-4743) - the current mapping is Jackrabbit 2.14 -> Oak trunk (UNTIL OAK 1.6 BRANCHES, THEN IT'LL BE 2.15), Jackrabbit 2.14 -> Oak 1.6 (ONCE BRANCHED), Jackrabbit 2.12 -> Oak 1.4 and 1.2, Jackrabbit 2.8 -> Oak 1.0)
+15. If the release was a stable release for which we publish API docs (such as Jackrabbit), consider updating the live site (https://svn.apache.org/repos/asf/jackrabbit/site/live/ - when producing the API docs, use a checkout of the actual release, specify an English locale (-Dlocale=en) and try to pick the right JDK version to minimize changes over the previously checked in docs).
Steps to build the release artifacts