On Mon, 2016-02-08 at 14:16 -0800, Junio C Hamano wrote: > Jeff King <peff@xxxxxxxx> writes: > > > FWIW, as the person who wrote that section, I think that is a good > > addition. We do have a link to Simon Tatham's bug-reporting guide, > > but > > this is a good place to put project-specific advice. > > > > In addition to "try it on next" you may want to also mention "try > > it on > > the latest version of git". That is another frequently given > > pointer to > > bug reporters. Trying "next" is obviously a superset, but I > > suspect > > trying a released version may be an easier first step for some > > people. > > Yes, definitely. > > I agree that testing with the latest released version would > typically be much easier to end users than building from the source. > It would reduce the need for "Ah, that's ancient issue, we know it > was fixed a few releases ago." responses by us; I do not recall many > of such responses in the recent history on the list, though. > > For the ones who are more into the spirit of helping each other who > can build from the source to help us even more, checking 'master' > and finding regressions before it gets too late is a very good > thing. Checking 'next' and confirming an upcoming fix is equally > valuable. While researching an unrelated issue, I stumbled upon http://marc.info/?l=git&m=142714670111063&w=2, which seems to have even more valuable information about community processes. Is there any interest in making this information discoverable from https://git-scm.com/community and/or the man pages? I'm happy to file an issue or to write a patch that adds a link, but I don't see myself spending more time on it than that. Matt -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html