jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From thom...@apache.org
Subject svn commit: r1620515 - /jackrabbit/site/live/JCR/creating-releases.html
Date Tue, 26 Aug 2014 06:45:25 GMT
Author: thomasm
Date: Tue Aug 26 06:45:25 2014
New Revision: 1620515

URL: http://svn.apache.org/r1620515
Log:
Improved release docs

Modified:
    jackrabbit/site/live/JCR/creating-releases.html

Modified: jackrabbit/site/live/JCR/creating-releases.html
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/JCR/creating-releases.html?rev=1620515&r1=1620514&r2=1620515&view=diff
==============================================================================
--- jackrabbit/site/live/JCR/creating-releases.html (original)
+++ jackrabbit/site/live/JCR/creating-releases.html Tue Aug 26 06:45:25 2014
@@ -113,10 +113,14 @@ but anyone is welcome to help test the r
 	<LI>Make sure that an appropriate version for the release is entered in Jira and that
all the related issues have been resolved.
 	This is also a good time to create a new version in JIRA for the next release.</LI>
 	<LI>Create a <TT>RELEASE-NOTES.txt</TT> file in the root folder of the
project to be released. 
-	If such a file already exists, update it for the release. When done, commit the file. 
+	If such a file already exists, update it for the release. 
 	See <A href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10591&version=12319480"
class="external-link">previous release notes</A> 
 	for examples of what to include. 
-	The release note report in Jira is a useful source of required information.</LI>
+	The release note report in Jira is a useful source of required information:
+	Open the <a href="https://issues.apache.org/jira/browse/OAK">Jira Oak page</a>,
+	click on the release, then on the "Release Notes" button on the top right.
+	When done, commit the file. 
+	</LI>
 	<LI>Build and deploy the release artifacts with Maven. See <A href="#CreatingReleases-ReleaseArtifacts">below</A>
for the exact steps.</LI>
 	<LI>Close the <A href="https://repository.apache.org/index.html#stagingRepositories"
class="external-link">staged repository</A> on repository.apache.org.</LI>
 	<LI>Upload the artifacts to 
@@ -175,6 +179,17 @@ but anyone is welcome to help test the r
 guide for more details. Make sure you have added the pgp key information in you maven settings
file, 
 especially if you have more than one key installed locally. 
 See <A href="#CreatingReleases-AppendixB">Appendix B</A> for the details.</P>
+<p>
+In case you don't feel comfortable to keep the passwords in the file 
+<code>~/.m2/settings.xml</code>
+forever, you need to set it now temporarily.
+</p>
+<p>
+There have been some problems with certain combinations of Java and Maven versions.
+A known combinations where releasing was successful is Java 7 with Maven 3.2.2.
+In case you get an exception "Proxy Error" in the <code>release:perform</code>,
see the 
+<a href="http://status.apache.org/">Apache Services Status Page</a>.
+</p>
 
 <OL>
 	<LI>Execute <TT>mvn release:prepare</TT>. This will update the POM files
and tag the release in svn.</LI>
@@ -184,6 +199,11 @@ See <A href="#CreatingReleases-AppendixB
 	You only need to add the keyname if you have multiple keys and the code signing keys is
not your default key.</LI>
 </OL>
 
+<p>
+After this is done, you can remove the passwords from the file 
+<code>~/.m2/settings.xml</code> if you don't want to keep it there.
+</p>
+
 
 <H2><A name="CreatingReleases-RelatedLinks"></A>Related Links</H2>
 



Mime
View raw message