On Fri, Jun 5, 2015 at 10:07 AM, Christian Couder <christian.cou...@gmail.com> wrote: > On Fri, Jun 5, 2015 at 7:56 AM, Gondek, Andreas > <andreas.gon...@dwpbank.de> wrote: >> Thanks, thanks, thanks. >> >> One last question. If I don't want to compile Git myself, how long may the >> pu branch take approx. to get into a next release? > > According to: > > https://github.com/git/git/blob/master/Documentation/howto/maintain-git.txt > > "One release cycle for a feature release is expected to last for eight > to ten weeks."
Actually I should have read the next lines that say: "- Maintenance releases are numbered as vX.Y.Z and are meant to contain only bugfixes for the corresponding vX.Y.0 feature release and earlier maintenance releases vX.Y.W (W < Z)." > As v2.4.2 was tagged on May 26, the next feature release should be in > 6 to 9 weeks, and will hopefully include the feature you are > interested in. The last feature release was v2.4.0 that was tagged on April 30, so the next one should be in 3 to 5 weeks. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
