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

[re...@apache.org]

Author: reschke
Date: Wed Apr 15 07:56:37 2020
New Revision: 1876536

URL: http://svn.apache.org/viewvc?rev=1876536&view=rev
Log:
add a note about checking non-interactive commits working before trying to prepare the release

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=1876536&r1=1876535&r2=1876536&view=diff
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/creating-releases.md (original)
+++ jackrabbit/site/trunk/src/site/markdown/creating-releases.md Wed Apr 15 07:56:37 2020
@@ -156,6 +156,11 @@ In case you don't feel comfortable to ke
 
 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 `release:perform`, see the [Apache Services Status Page](http://status.apache.org/), however it has been reported that the status page is not always accurate. In case you get an error with respect to API incompatibilities, try with an older Maven version or enforce use of a newer release plugin, such as with `mvn org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare`.
 
+Note that preparing the release requires a tagging operation in the source
+repository. Make sure upfront that non-interactive commits work 
+(like `svn commit -m 'commit message'`) without prompting for credentials, otherwise
+the tagging step will fail.
+
 1. Execute mvn `release:prepare`. This will update the POM files and tag the release in svn (see [Appendix F](#Appendix_F:_Version_Numbers) for how version numbers change).
 2. Execute mvn `release:perform`. This will build the tagged release and deploy the artifacts to a staging repository on repository.apache.org. The non-Maven release artifacts are automatically deployed to your home directory on people.apache.org. You only need to add the keyname if you have multiple keys and the code signing keys is not your default key.