Meta/MaintNotes: post 1.8.1
Junio C Hamano committed
Dec 31, 2012 at 15:45 UTC
bc5e9bbe5b8ed12ed4a8d851bd0f1a488995c2ea
1 file changed
+8
-6
MaintNotes
+8
-6
@@ -108,18 +108,20 @@ There are four branches in git.git repository that track the source tree
108
of git: "master", "maint", "next", and "pu".
109
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.8.0 done on
114
-Oct 21, 2012. You can expect that the tip of the "master" branch is always
115
-more stable than any of the released versions.
111
+ready to be used in a production setting. Every now and then, a
112
+"feature release" is cut from the tip of this branch and they
113
+typically are named with three dotted decimal digits. The last such
114
+release was 1.8.1 done on Dec 31, 2012 (or Jan 1, 2013, depending on
115
+where you were when it happened). You can expect that the tip of the
116
+"master" branch is always more stable than any of the released
117
+versions.
118
119
Whenever a feature release is made, "maint" branch is forked off from
120
"master" at that point. Obvious, safe and urgent fixes after a feature
121
release are applied to this branch and maintenance releases are cut from
122
it. The maintenance releases are named with four dotted decimal, named
123
after the feature release they are updates to; the last such release was
122
-1.8.0.2. New features never go to this branch. This branch is also
124
+1.8.0.3. New features never go to this branch. This branch is also
125
merged into "master" to propagate the fixes forward as needed.
126
127
A new development does not usually happen on "master". When you send a