1 How to create a Windows Release
2 ===============================
4 A setup executable is named as follows
6 - followed by the official git.git version indicating the core features;
8 * preview<date>, for snapshot builds.
9 * beta#, if we reached a certain quality level but know we're not
10 ready for a stable release. For example testing is needed.
11 * rc#, if there are no known issues. If no new bugs are found, this
12 can be upgraded to a stable release.
16 Git-1.5.3-preview20071014.exe
21 We'll not necessary reach a stable release for each official version
22 number. If we merge changes from git.git we will adjust the number.
23 For example, we might jump to Git-1.5.3.3-rc1 without ever releasing
24 Git-1.5.3. We should stay with preview/beta/rc until we have reached
27 We use the following criteria to decide if we go stable.
28 * features equivalent to official git-#-#-# are available in Git Bash.
29 * [DONE] git-gui works if run from Git Bash.
30 * [DONE] git-gui works if run from Start Menu.
31 * [DONE] git and git-gui available from Windows Command Prompt (cmd shell).
32 * server functionality (git-daemon, git-shell, ...) _not_ necessarily
34 * git-cheetah _not_ needed.
36 For now we should only release previews.
39 He are the step by step instructions for the maintainer:
45 git merge mingw/master
48 make -k test | tee test.log
50 git push . devel:master # should fast-forward
54 git checkout origin/html
58 start ReleaseNotes.rtf # edit and save
60 git push . devel:master
61 git tag -a -m "Git-<version>"
62 ./release.sh <version>
65 # upload to Google code (verify sha1)
70 git push Git-<version> # don't forget to push tag
72 # reply to Junio's announcement