Matt McCutchen <matt@xxxxxxxxxxxxxxxxx> writes: > See my revised proposed text here: > > https://github.com/git/git-scm.com/pull/676/files If somebody says "The ancient version I use has this bug, it does not reproduce with 'next'", the first thing we would ask would be "Does it still happen on 'master'?" Even though it is often clear from the context and the nature of the bug which topic in 'next' is likely to have fixed it, if the reporter skipped 'master', we would end up scratching our head which topic in 'next' that is not 'master' fixed it as a side effect. And because not everything on 'next' is ready for 'master', we cannot just merge everything ;-) On the other hand, if somebody says "The ancient version I use has this bug, it does not reproduce with 'master'", we would likely not to say anything other than "Oh, that's good for you.". If somebody says "The ancient version I use has this bug, it still reproduces with 'master'", then we would ask 'next' to be tried. For these reasons, I'd say "try the 'master' branch". Trying 'next' is highly appreciated, but not without trying 'master'. > I left a mention of providing feedback on pending fixes but thought it > would be too much to go into the details of how to identify whether > there is a pending fix. What is in 'master' relative to the version of Git the bug reporter has can be seen by reading through RelNotes of the released versions since the version reporter used, and RelNotes in the 'master'. Every time an updated 'master' is pushed out, the changes made by the topics merged to it are added to update RelNotes. "What's cooking" report, issued once or twice a week, summarizes the topics that are still not in 'master' (the description in there are used to update RelNotes when topics graduate to 'master'). Also "Git Rev News" may cover recent efforts on tackling interesting bugs. Thanks. -- 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