svn commit: r786989 - /websites/staging/aries/trunk/content/development/versionpolicy.html

[bu...@apache.org]

Author: buildbot
Date: Tue Mar 15 09:32:15 2011
New Revision: 786989

Log:
Staging update by buildbot

Modified:
    websites/staging/aries/trunk/content/development/versionpolicy.html

Modified: websites/staging/aries/trunk/content/development/versionpolicy.html
==============================================================================
--- websites/staging/aries/trunk/content/development/versionpolicy.html (original)
+++ websites/staging/aries/trunk/content/development/versionpolicy.html Tue Mar 15 09:32:15 2011
@@ -270,8 +270,15 @@ recent release of the package and not to
 <li>
 <p>Scenario 2, making changes to a package with released version a.b.c</p>
 </li>
-<li>Developer A fixes a bug in the package and increments it's version to a.b.c+1</li>
-<li>Developer B makes an API breaking change and increases the package version to (a+1).0.0</li>
+<li>Developer A adds a method to an interface in the package and increments it's version to a.b+1.0</li>
+<li>
+<p>Developer B fixes a bug in the package, leaves its version at a.b+1.0</p>
+</li>
+<li>
+<p>Scenario 3, making changes to a package with released version a.b.c</p>
+</li>
+<li>Developer A fixes a bug in the package, and increments its version to a.b.c+1</li>
+<li>Developer B deletes a method from an interface and increases the package version to a+1.0.0</li>
 </ul>
 <h2 id="importing_packages">Importing packages</h2>
 <p>The bnd default version range policy for imports is the consumer policy (==, +), you may need to