Author: zoe
Date: Wed Feb 9 14:54:42 2011
New Revision: 1068921
URL: http://svn.apache.org/viewvc?rev=1068921&view=rev
Log:
para
Modified:
aries/site/trunk/content/development/ReleaseProcessRequirements.mdtext
Modified: aries/site/trunk/content/development/ReleaseProcessRequirements.mdtext
URL:
http://svn.apache.org/viewvc/aries/site/trunk/content/development/ReleaseProcessRequirements.mdtext?rev=1068921&r1=1068920&r2=1068921&view=diff
==============================================================================
--- aries/site/trunk/content/development/ReleaseProcessRequirements.mdtext
(original)
+++ aries/site/trunk/content/development/ReleaseProcessRequirements.mdtext Wed
Feb 9 14:54:42 2011
@@ -43,7 +43,7 @@ and maintain our own alternative, to all
<p>The consequence of not bumping the major version and using the versioning
tool to compare versions in trunk (for the next release from trunk)
and using the versioning tool to create bug fix versions from the branch has
the potential to lead to the situation in which bundles with the
same version number have different content.
-For example, as time goes on another release (version 6) of the proxy module
is created, the version compare tool dictates that proxy-impl
+<p>For example, as time goes on another release (version 6) of the proxy
module is created, the version compare tool dictates that proxy-impl
should be released at version 0.4.2. But now, someone who wants a fix to
proxy-impl in 0.4.1 (in proxy module version 5) which would be provided
from the branch, would also get a proxy-impl bundle at version 0.4.2 with
different content. This is a situation which must be avoided.
