Re: What's cooking in git.git (Jun 2020, #01; Wed, 3)
- From
Philip Oakley <philipoakley@iee.email>
- Date
- Jun 6, 2020, 13:57 UTC
- Message-ID
- <ca05688f-4f03-97b4-7f88-a4fc89bc119a@iee.email>
- In-Reply-To
- <CABPp-BFLUZvycq_o6mPcx3ZQkeQy79nQ_mGD3B+JLzBwb6ER=g@mail.gmail.com>
On 05/06/2020 02:46, Elijah Newren wrote:
Show 9 quoted lines
> Another consideration we could make is just scheduling .1 releases > automatically, and not limiting them to security fixes but instead > considering the same kinds of things that would be allowed around the > time of -rc1 or -rc2. I still want to push to make the quality of .0 > releases as high as we can, but given that human nature seems to lean > towards avoiding things until they are labelled as official, and since > we benefit from that wider feedback, maybe we adjust slightly to take > advantage of natural behavior and do .1 releases? Anyway, just a > thought.
Maybe simply tag the current master every 2 weeks of the cycle (.wk2, .wk4, wk6), as appropriate, just to give potential users/testers a stake in the ground to reference to.
Or maybe a 'mid cycle' .mc1 release for a similar 'nudge' effect [1] of 'try this one'.
Philip
[1] https://en.wikipedia.org/wiki/Nudge_theory