On 04-06-2020 20:02, Christian Couder wrote: > > Now to go back to Junio's question: > >> ... people are eager >> enough to help by reporting issues they encounter, but there are not >> enough people who are eager enough to help by testing the tip of >> 'master' before the release. Are there things we can do to help >> them become early adopters so that they do not have to scramble >> after the release? > > Yeah, I agree that increasing the number of early adopters could be > the best way to avoid regressions report just after the release. > > Maybe we could just ask people to test rc releases or 'master' in Git > Rev News? That sounds like a good idea. > It might work better if someone wrote a small article about > what is coming in the next release before asking to test. I think writing an article wouldn't need much effort thanks to the wonderful summaries of the topics already found in the '-rc' release e-mails. It might need curation as there would be a lot of topics. > Then there > is the issue of making it easier to build Git and to understand and > fix build issues. Yeah, that would be nice. As a first step we could link to steps for building Git from the hypothetical article about the '-rc'. The "Install Dependencies" section of MyFirstContribution is an option[1]. [1]: https://git-scm.com/docs/MyFirstContribution#dependencies > We could also perhaps coordinate Git Rev News > editions and Git releases, so that the editions are published for > example between rc-1 and rc-2 releases. > That would be necessary. Though, I'm wondering how the eight to ten week feature release cycle of Git and monthly frequency of Rev News would play along. This might need some thought. -- Sivaraam
