[asterisk-dev] Proposal for New Major Version Process Change
dan at nimblea.pe
Wed Jul 8 08:24:31 CDT 2020
YES YES YES.
I never really got why it was done like it was...
I agree, 4-6 weeks is good. If someone's going to take the time to upgrade
to an 18 RC then they'll be looking to test it and give feedback etc etc so
you don't need a huge amount of time... just enough to actually action bug
fixes and then release new RCs with those bug fixes
On Wed, Jul 8, 2020 at 2:14 PM Joshua C. Colp <jcolp at sangoma.com> wrote:
> On Wed, Jul 8, 2020 at 9:56 AM Jared Smith <jaredsmith at jaredsmith.net>
>> On Wed, Jul 8, 2020 at 8:21 AM Joshua C. Colp <jcolp at sangoma.com> wrote:
>>> 1. It leaves a confusing area for developers where we have to ask
>>> "should this go into 18.0?"
>>> 2. It confuses users because if they upgrade to 18.0.0 then it is likely
>>> the other current releases have bug fixes they don't have, which has caused
>>> issues for users in the past.
>> I agree with these two points of confusion.
>> What do people think? Do we believe that a month out is ample enough?
>> I think somewhere between four and six weeks is more than adequate, given
>> the maturity of the project.
> That's my thinking too. I also think despite not creating actual tarballs
> we could still reach out on the asterisk-users list and the Discourse early
> to inform people that the branch has been created and while a release
> candidate has not yet been created that it can still be retrieved from Git
> or Github and used/tested.
> Joshua C. Colp
> Asterisk Technical Lead
> Sangoma Technologies
> Check us out at www.sangoma.com and www.asterisk.org
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the asterisk-dev