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 2018/11/05 05:54:13 UTC
svn commit: r1845755 -
/jackrabbit/site/trunk/src/site/markdown/creating-releases.md
Author: reschke
Date: Mon Nov 5 05:54:13 2018
New Revision: 1845755
URL: http://svn.apache.org/viewvc?rev=1845755&view=rev
Log:
fix typo that reversed the intended meaning
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=1845755&r1=1845754&r2=1845755&view=diff
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/creating-releases.md (original)
+++ jackrabbit/site/trunk/src/site/markdown/creating-releases.md Mon Nov 5 05:54:13 2018
@@ -271,7 +271,7 @@ Appendix E: Version Changes
**HERE BE DRAGONS**
-In general, changes in stable branches should not change export versions, in order to create version conflicts with the ongoing development on the unstable branch. So avoid, avoid, avoid!
+In general, changes in stable branches should not change export versions, in order to avoid version conflicts with the ongoing development on the unstable branch. So avoid, avoid, avoid!
If the version change really is required, then it is mandatory to check that the new API is identical with the API in other release branches with the same version number.