summaryrefslogtreecommitdiff
path: root/debian
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <junkio@cox.net>2005-12-21 22:33:37 -0800
committerLibravatar Junio C Hamano <junkio@cox.net>2005-12-21 22:33:37 -0800
commitc894168631e4b7da66ed3993a4c92380d38599a8 (patch)
tree39a70bec4fc08119b0c65d32a37c6345db43d156 /debian
parentMerge branch 'fixes' (diff)
downloadtgif-c894168631e4b7da66ed3993a4c92380d38599a8.tar.xz
Versioning scheme changes.
HPA suggests it is simply silly to imitate Linux versioning scheme where the leading "2" does not mean anything anymore, and I tend to agree. The first feature release after 1.0.0 will be 1.1.0, and the development path leading to 1.1.0 will carry 1.0.GIT as the version number from now on. Similarly, the third maintenance release that follows 1.0.0 will not be 1.0.0c as planned, but will be called 1.0.3. The "maint" branch will merge in fixes and immediately tagged, so there is no need for 1.0.2.GIT that is in between 1.0.2 (aka 1.0.0b) and 1.0.3. Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'debian')
-rw-r--r--debian/changelog6
1 files changed, 6 insertions, 0 deletions
diff --git a/debian/changelog b/debian/changelog
index 491ebd9ba2..084e37a37a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+git-core (1.0.GIT-0) unstable; urgency=low
+
+ * Post GIT 1.0 development track.
+
+ -- Junio C Hamano <junkio@cox.net> Wed, 21 Dec 2005 22:28:33 -0800
+
git-core (1.0.0.GIT-0) unstable; urgency=low
* Post GIT 1.0.0 development track.