I propose to simplify our release numbering scheme as described below.
Opinions?
Steffen
commit 1f6250028e90947b23b93ba9a8264eabf79c239b
Author: Steffen Prohaska <[EMAIL PROTECTED]>
Date: Sun Feb 3 00:03:57 2008 +0100
HowToRelease: Simplify release numbering scheme
The version scheme is modified to address the following issues
- The old scheme was too complex: beta is removed.
- The msysgit scheme should be clearly different from the official
version: We use winrc instead of rc.
- Snapshot releases from the current master that are unrelated to
any official version should not carry an official version
number:
Such releases will not contain any version number, but simply
preview<DATE>.
We also add two criteria that should be met before we go stable
- safe CRLF handling.
- handling of case insensitive filesystems.
Signed-off-by: Steffen Prohaska <[EMAIL PROTECTED]>
diff --git a/share/WinGit/HowToRelease.txt b/share/WinGit/
HowToRelease.txt
index 32bee2f..a7ad639 100644
--- a/share/WinGit/HowToRelease.txt
+++ b/share/WinGit/HowToRelease.txt
@@ -2,30 +2,33 @@ How to create a Windows Release
===============================
A setup executable is named as follows
-- it starts with Git;
-- followed by the official git.git version indicating the core
features;
-- followed by
+ - it starts with Git;
+ - followed by the official git version if the release is closely
+ related to a specific version of official git;
+ - followed by
* preview<date>, for snapshot builds.
- * beta#, if we reached a certain quality level but know we're not
- ready for a stable release. For example testing is needed.
- * rc#, if there are no known issues. If no new bugs are found, this
- can be upgraded to a stable release.
+ * winrc#, if we reach a certain quality level and plan to release
+ a stable version. If no bugs are found, this can be upgraded
+ to a stable release. We use winrc instead of simply rc to avoid
+ confusion with official release candidates. The prefix "win"
+ clearly indicates that the tag is about the Windows release.
Examples:
-Git-1.5.3-preview20071014.exe
-Git-1.5.3-beta1.exe
-Git-1.5.3-rc1.exe
-Git-1.5.3.exe
+Git-preview20080313.exe
+Git-1.5.4-preview20071014.exe
+Git-1.5.4-winrc3.exe
+Git-1.5.4.exe
-We'll not necessary reach a stable release for each official version
+We'll not necessary release a stable version for each official version
number. If we merge changes from git.git we will adjust the number.
-For example, we might jump to Git-1.5.3.3-rc1 without ever releasing
-Git-1.5.3. We should stay with preview/beta/rc until we have reached
-sufficient stability.
+We will continue releasing previews until we have reached sufficient
+stability.
-We use the following criteria to decide if we go stable.
+The following criteria should be met before we go stable.
* features equivalent to official git-#-#-# are available in
Git Bash.
+ * safe crlf handling.
+ * good support for case insensitive filesystems.
* [DONE] git-gui works if run from Git Bash.
* [DONE] git-gui works if run from Start Menu.
* [DONE] git and git-gui available from Windows Command Prompt
(cmd shell).
