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

[zo...@apache.org]

Author: zoe
Date: Tue Mar 15 09:54:17 2011
New Revision: 1081706

URL: http://svn.apache.org/viewvc?rev=1081706&view=rev
Log:
try subheadings instead

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=1081706&r1=1081705&r2=1081706&view=diff
==============================================================================
--- aries/site/trunk/content/development/versionpolicy.mdtext (original)
+++ aries/site/trunk/content/development/versionpolicy.mdtext Tue Mar 15 09:54:17 2011
@@ -42,19 +42,19 @@ Developers **must** increment the versio
 semantic versioning when they make changes to a package. The version should relate to the most
 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
+#### 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 
 
 
- * Scenario 2, making changes to a package with released version a.b.c
+#### 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
+#### 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