KEP-0005.txt

[Jeroen van Meeuwen]

 KEP-0005.txt |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

New commits:
commit a70b998bd76ca7ebcb7906f4e7495ae3a33abe0d
Author: Jeroen van Meeuwen (Kolab Systems) <vanmeeuwen at kolabsys.com>
Date:   Mon Mar 14 13:23:50 2011 +0000

    Adjust the title to indicate KEP #5 concerns Server Product Versioning
    Clarify the example exception to the rule of thumb for teeny pre-releases

diff --git a/KEP-0005.txt b/KEP-0005.txt
index 066ceaf..63ab1d8 100644
--- a/KEP-0005.txt
+++ b/KEP-0005.txt
@@ -1,7 +1,7 @@
 {{kep
  |number=5
  |ticketnumber=
- |title=Product Versioning
+ |title=Server Product Versioning
  |author=Jeroen van Meeuwen
  |author_email=vanmeeuwen at kolabsys.com
  |status=draft
@@ -82,7 +82,7 @@ Upstream pre-releases are often simply appended to the ''x.y.z'' version: ''x.y.
 
 Since, in conjunction with the aforementioned product versioning semantics, ''z'' in the situations of pre-releases is usually 0. Skipping the 0 in the product version entirely solves the complete problem. A ''beta1'' pre-release for ''2.5.0'', which would traditionally become ''2.5.0-beta1'', would then become ''2.5-beta1'', allowing for an update to the ''2.5.0'' final version.
 
-{{note|Exceptions for Unstable Bug-fix Releases|Exceptions can be made for bug-fix releases deemed unstable -maybe the bug-fix touched critical code and warrants testing. In such cases, consider using a one-time 4-octet release: ''x.y.z-rc1'' for the pre-release, and ''x.y.z.'''0''''' for the final release; ''x.y.(z+1)'' can then upgrade from the final release.}}
+{{note|Exceptions for Unstable Bug-fix Releases|Exceptions can be made for bug-fix releases deemed unstable -maybe the bug-fix touched critical code and warrants testing. In such cases, consider using a one-time 4-octet release: ''x.y.z-rc1'' for the pre-release, and ''x.y.z.'''0''''' for the final release; ''x.y.(z+1)'' can then upgrade from the final release. Be aware this type of exception only applies to pre-releases for bug-fix releases, should they be needed, as opposed to the general rule applying to pre-releases for Minor version component increments.}}
 
 ==== Releases and Native Packaging ====