MaintNotes update after 1.7.2
Junio C Hamano committed
Jul 21, 2010 at 15:14 UTC
6dc291c786d21f0bdfb60c79a7bbf2d24d0c1d48
1 file changed
+5
-4
MaintNotes
+5
-4
@@ -96,7 +96,7 @@ minor breakages or brown paper bag bugs but they are not expected to be
96
anything major, and more importantly quickly and trivially fixable. Every
97
now and then, a "feature release" is cut from the tip of this branch and
98
they typically are named with three dotted decimal digits. The last such
99
-release was 1.7.0 done on Feb 12, 2010. You can expect that the tip of
99
+release was 1.7.2 done on Jul 21, 2010. You can expect that the tip of
100
the "master" branch is always more stable than any of the released
101
versions.
102
@@ -105,7 +105,7 @@ Whenever a feature release is made, "maint" branch is forked off from
105
release are applied to this branch and maintenance releases are cut from
106
it. The maintenance releases are named with four dotted decimal, named
107
after the feature release they are updates to; the last such release was
108
-1.6.6.2. New features never go to this branch. This branch is also
108
+1.7.1.1. New features never go to this branch. This branch is also
109
merged into "master" to propagate the fixes forward.
110
111
A trivial and safe enhancement goes directly on top of "master". A new
@@ -202,8 +202,9 @@ I have relied on and expect to continue relying on heavily:
202
- Linus on general design issues.
203
204
- Linus, Shawn Pearce, Johannes Schindelin, Nicolas Pitre, René
205
- Scharfe, Jeff King and Johannes Sixt on general implementation
206
- issues.
205
+ Scharfe, Jeff King, Jonathan Nieder, Johan Herland, Johannes Sixt,
206
+ and Sverre Rabbelier on general implementation issues and reviews
207
+ on the mailing list.
208
209
- Shawn and Nicolas Pitre on pack issues.
210