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>
Junio C Hamano committed
Dec 21, 2005 at 22:33 UTC
c894168631e4b7da66ed3993a4c92380d38599a8
2 files changed
+7
-1
Makefile
+1
-1
@@ -55,7 +55,7 @@ all:
55
# Define USE_STDEV below if you want git to care about the underlying device
56
# change being considered an inode change from the update-cache perspective.
57
58
-GIT_VERSION = 1.0.0.GIT
58
+GIT_VERSION = 1.0.GIT
59
60
# CFLAGS and LDFLAGS are for the users to override from the command line.
61
debian/changelog
+6
@@ -1,3 +1,9 @@
1
+git-core (1.0.GIT-0) unstable; urgency=low
2
+
3
+ * Post GIT 1.0 development track.
4
+
5
+ -- Junio C Hamano <junkio@cox.net> Wed, 21 Dec 2005 22:28:33 -0800
6
+
7
git-core (1.0.0.GIT-0) unstable; urgency=low
8
9
* Post GIT 1.0.0 development track.