2 commits - KEP-0005.txt

[Jeroen van Meeuwen]

 KEP-0005.txt |   26 +++++++++++++++++++-------
 1 file changed, 19 insertions(+), 7 deletions(-)

New commits:
commit 4500743fb75277865809fc6adf2b80feef47b452
Author: Jeroen van Meeuwen (Kolab Systems) <vanmeeuwen at kolabsys.com>
Date:   Wed Aug 24 11:28:38 2011 +0100

    Update KEP #5 with APT packaging specific notes

diff --git a/KEP-0005.txt b/KEP-0005.txt
index 94fd1e0..a19d712 100644
--- a/KEP-0005.txt
+++ b/KEP-0005.txt
@@ -105,11 +105,23 @@ For a pre-release of product X.Y.Z, the ''release'' component in packaging shall
 
 Such would build package file names such as:
 
- kolabd-2.3-0.1.beta1.el5
- kolabd-2.3-0.2.beta1.el5
- kolabd-2.3-0.3.beta2.el5
- kolabd-2.3-0.4.rc1.el5
- kolabd-2.3.0-1.el5
+ kolabd-2.3-0.1.beta1.el5       (initial upstream 2.3 beta1 release packaged for the Enterprise Linux 5 RPM-based distribution)
+ kolabd-2.3-0.2.beta1.el5       (initial upstream 2.3 beta1 release with packaging fix)
+ kolabd-2.3-0.3.beta2.el5       (initial upstream 2.3 beta2 release)
+ kolabd-2.3-0.4.rc1.el5         (initial upstream 2.3 release candidate 1 release)
+ kolabd-2.3.0-1.el5             (initial, final upstream 2.3.0 release)
+
+For Debian (APT) packaging, this would be along the lines of:
+
+ kolabd-2.3~beta1-0.1           (initial upstream 2.3 beta1 release packaged for current stable Debian)
+ kolabd-2.3~beta1-0.1~bpo50+1   (initial upstream 2.3 beta1 release packaged for current old-stable Debian (bpo50, where '50'
+                                is supposed to indicate the Debian release version number the package is backported to))
+ kolabd-2.3~beta1-0.2           (initial upstream 2.3 beta1 release with packaging fix)
+ kolabd-2.3~beta2-0.3           (initial upstream 2.3 beta2 release)
+ kolabd-2.3~rc1-0.4             (initial upstream 2.3 release candidate 1 release)
+ kolabd-2.3.0-1                 (initial, final upstream 2.3.0 release)
+
+{{note|Debian Version and Release Comparison Routine Requirement|Given that the DPKG compares epoch, upstream version and debian version much alike RPM does <ref name="dpkg-version-compare">http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version</ref>, it's policy depicts the upstream release is part of the upstream version component (i.e. ''2.3~beta2'' is the upstream version). This requires packagers to acknowledge upstream will have to name their pre-releases in alphabetical order which is most often the case for alpha, beta and rc releases, but does not necessarily have to hold true under all circumstances such as with a prealpha release<ref name="wikipedia-software-release-cycles">http://en.wikipedia.org/wiki/Software_release_life_cycle</ref>.}}
 
 == References ==
 


commit 7d18cb978689221dc7e073565ba834d26b10b3ca
Author: Jeroen van Meeuwen (Kolab Systems) <vanmeeuwen at kolabsys.com>
Date:   Wed Aug 24 11:07:14 2011 +0100

    Correct the use of SHOULD not vs. SHOULD NOT

diff --git a/KEP-0005.txt b/KEP-0005.txt
index 1c2c25f..94fd1e0 100644
--- a/KEP-0005.txt
+++ b/KEP-0005.txt
@@ -74,7 +74,7 @@ The Teeny Version '''SHALL''' only be incremented for bug-fix releases. Included
 
 === Release ===
 
-Regular releases are versioned ''x.y.z'',  using the regular versioning schema, but pre-releases '''SHOULD''' not be versioned ''x.y.z''.
+Regular releases are versioned ''x.y.z'',  using the regular versioning schema, but pre-releases '''SHOULD NOT''' be versioned ''x.y.z''.
 
 ==== Pre-releases ====
 
@@ -117,4 +117,4 @@ Such would build package file names such as:
 
 == Copyright ==
 
-This document is placed in the public domain.
\ No newline at end of file
+This document is placed in the public domain.