You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@aries.apache.org by zo...@apache.org on 2011/03/15 10:43:01 UTC

svn commit: r1081699 - /aries/site/trunk/content/development/versionpolicy.mdtext

Author: zoe
Date: Tue Mar 15 09:43:00 2011
New Revision: 1081699

URL: http://svn.apache.org/viewvc?rev=1081699&view=rev
Log:
bullet points!

Modified:
    aries/site/trunk/content/development/versionpolicy.mdtext

Modified: aries/site/trunk/content/development/versionpolicy.mdtext
URL: http://svn.apache.org/viewvc/aries/site/trunk/content/development/versionpolicy.mdtext?rev=1081699&r1=1081698&r2=1081699&view=diff
==============================================================================
--- aries/site/trunk/content/development/versionpolicy.mdtext (original)
+++ aries/site/trunk/content/development/versionpolicy.mdtext Tue Mar 15 09:43:00 2011
@@ -43,16 +43,21 @@ semantic versioning when they make chang
 recent release of the package and not to the version found in trunk. For example:
 
  * Scenario 1, making changes to a package with released version a.b.c
-   * Developer A fixes a bug in the package and increments it's version to a.b.c+1
-   * Developer B fixes another bug in the package but leaves the version at a.b.c+1 
+
+   1. Developer A fixes a bug in the package and increments it's version to a.b.c+1
+   2. Developer B fixes another bug in the package but leaves the version at a.b.c+1 
+
 
  * Scenario 2, making changes to a package with released version a.b.c
-   * Developer A adds a method to an interface in the package and increments it's version to a.b+1.0
-   * Developer B fixes a bug in the package, leaves its version at a.b+1.0
 
-* Scenario 3, making changes to a package with released version a.b.c
-   * Developer A fixes a bug in the package, and increments its version to a.b.c+1
-   * Developer B deletes a method from an interface and increases the package version to a+1.0.0
+   1. Developer A adds a method to an interface in the package and increments it's version to a.b+1.0
+   1. Developer B fixes a bug in the package, leaves its version at a.b+1.0
+
+ 
+ * Scenario 3, making changes to a package with released version a.b.c
+
+   1. Developer A fixes a bug in the package, and increments its version to a.b.c+1
+   1. Developer B deletes a method from an interface and increases the package version to a+1.0.0