[asterisk-dev] Proposal for New Major Version Process Change

Joshua C. Colp jcolp at sangoma.com
Wed Jul 8 08:12:14 CDT 2020

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?
>> <http://lists.digium.com/mailman/listinfo/asterisk-dev>
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20200708/d6ef17dc/attachment.html>

More information about the asterisk-dev mailing list