Update MaintNotes (post 1.7.12)
Junio C Hamano committed
Aug 19, 2012 at 20:15 UTC
5214548303a585b0da60d0da85dd618fb53c4086
1 file changed
+4
-4
MaintNotes
+4
-4
@@ -1,6 +1,6 @@
1
Subject: A note from the maintainer
2
3
-Welcome to git development community.
3
+Welcome to the Git development community.
4
5
This message is written by the maintainer and talks about how Git
6
project is managed, and how you can work with it.
@@ -110,8 +110,8 @@ of git: "master", "maint", "next", and "pu".
110
The "master" branch is meant to contain what are very well tested and
111
ready to be used in a production setting. Every now and then, a "feature
112
release" is cut from the tip of this branch and they typically are named
113
-with three dotted decimal digits. The last such release was 1.7.11 done on
114
-Jun 17, 2012. You can expect that the tip of the "master" branch is always
113
+with three dotted decimal digits. The last such release was 1.7.12 done on
114
+Aug 19, 2012. You can expect that the tip of the "master" branch is always
115
more stable than any of the released versions.
116
117
Whenever a feature release is made, "maint" branch is forked off from
@@ -119,7 +119,7 @@ Whenever a feature release is made, "maint" branch is forked off from
119
release are applied to this branch and maintenance releases are cut from
120
it. The maintenance releases are named with four dotted decimal, named
121
after the feature release they are updates to; the last such release was
122
-1.7.11.1. New features never go to this branch. This branch is also
122
+1.7.11.5. New features never go to this branch. This branch is also
123
merged into "master" to propagate the fixes forward.
124
125
A new development does not usually happen on "master". When you send a