Author: fchrist
Date: Thu Jan 24 14:20:05 2013
New Revision: 1438010
URL: http://svn.apache.org/viewvc?rev=1438010&view=rev
Log:
Fixed release:prepare command
Modified:
stanbol/site/trunk/content/development/release-management.mdtext
Modified: stanbol/site/trunk/content/development/release-management.mdtext
URL:
http://svn.apache.org/viewvc/stanbol/site/trunk/content/development/release-management.mdtext?rev=1438010&r1=1438009&r2=1438010&view=diff
==============================================================================
--- stanbol/site/trunk/content/development/release-management.mdtext (original)
+++ stanbol/site/trunk/content/development/release-management.mdtext Thu Jan 24
14:20:05 2013
@@ -34,18 +34,16 @@ staging repository.
To start a release we use the following command. We ensure that
'clean install' is executed first. Then we adjust the commit comment
-that will be generated by the release plugin. Additionally, we hinder
-the plugin to update dependencies to the new development version and
-we do not want to update our working copy version to use the new
-development version. Our goal is to cut the release and leave the
+that will be generated by the release plugin.
+
+Our goal is to cut the release and leave the
current trunk untouched as it was before. We will update versions after
the release vote has passed -- not before. That means that the values
-that you enter when asked for the next development version will
-never be used.
+that you enter when asked for the next development version should be
+the same development version as it was before.
$ mvn release:prepare -DpreparationGoals=clean install \
-DupdateDependencies=false \
- -DupdateWorkingCopyVersions=false \
-DscmCommentPrefix=STANBOL-XXX:
Please, replace the XXX with the corresponding Jira issue number.
