From 74e80c8a9166b4a6b23516265ce599097d2fcbfe Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Fri, 27 Jan 2012 13:36:08 -0800 Subject: [PATCH] MaintNotes: post 1.7.9 update --- MaintNotes | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/MaintNotes b/MaintNotes index fbffa4b9a9..ec3d71cf16 100644 --- a/MaintNotes +++ b/MaintNotes @@ -106,8 +106,8 @@ of git: "master", "maint", "next", and "pu". The "master" branch is meant to contain what are very well tested and ready to be used in a production setting. Every now and then, a "feature release" is cut from the tip of this branch and they typically are named -with three dotted decimal digits. The last such release was 1.7.8 done on -Dec 2, 2011. You can expect that the tip of the "master" branch is always +with three dotted decimal digits. The last such release was 1.7.9 done on +Jan 27, 2012. You can expect that the tip of the "master" branch is always more stable than any of the released versions. Whenever a feature release is made, "maint" branch is forked off from @@ -115,7 +115,7 @@ Whenever a feature release is made, "maint" branch is forked off from release are applied to this branch and maintenance releases are cut from it. The maintenance releases are named with four dotted decimal, named after the feature release they are updates to; the last such release was -1.7.7.4. New features never go to this branch. This branch is also +1.7.8.4. New features never go to this branch. This branch is also merged into "master" to propagate the fixes forward. A new development does not usually happen on "master". When you send a -- 2.47.3