Update MaintNotes post 1.7.6.1
Junio C Hamano committed
Aug 24, 2011 at 16:41 UTC
237b1100ed0414ba84587184184acf53da0b6e3d
1 file changed
+3
-3
MaintNotes
+3
-3
@@ -118,8 +118,8 @@ of git: "master", "maint", "next", and "pu".
118
The "master" branch is meant to contain what are very well tested and
119
ready to be used in a production setting. Every now and then, a "feature
120
release" is cut from the tip of this branch and they typically are named
121
-with three dotted decimal digits. The last such release was 1.7.5 done on
122
-Apr 24, 2011. You can expect that the tip of the "master" branch is
121
+with three dotted decimal digits. The last such release was 1.7.6 done on
122
+June 26, 2011. You can expect that the tip of the "master" branch is
123
always more stable than any of the released versions.
124
125
Whenever a feature release is made, "maint" branch is forked off from
@@ -127,7 +127,7 @@ Whenever a feature release is made, "maint" branch is forked off from
127
release are applied to this branch and maintenance releases are cut from
128
it. The maintenance releases are named with four dotted decimal, named
129
after the feature release they are updates to; the last such release was
130
-1.7.4.5. New features never go to this branch. This branch is also
130
+1.7.6.1. New features never go to this branch. This branch is also
131
merged into "master" to propagate the fixes forward.
132
133
A new development does not usually happen on "master". When you send a