I see. If we expect API instability, then a "0." release line is a helpful indicator.
--Chris Nauroth On 12/10/15, 10:53 AM, "Allen Wittenauer" <[email protected]> wrote: > >> On Dec 10, 2015, at 10:46 AM, Chris Nauroth <[email protected]> >>wrote: >> 1. How would people feel about calling it 1.0.0? Is there something >> specific we're hedging on by calling it a "0." release? > > For me, I know I¹m expecting there to still be quite a bit of movement >in the plug-in API. For example, I know I¹ve got a big change coming in >how the help usage is output. There¹s also a few ASF-specific bits that >need some cleanup with regards to non-ASF folks really getting the most >out of test-patch. > > >> 2. If I'm reading this correctly, you're suggesting weekly releases if >> there are code changes. With only 6 PMC members who have binding votes, >> it's a lot to ask of a small number of people. I see a risk of many of >> these votes fizzling out and expiring without getting enough binding >> votes. How would you feel about a longer regular cadence, such as >> monthly, with the option to invoke additional out-of-band releases as >> needed for critical fixes? > > > I think this is a great point. > > > Thanks!
