On Wed, Jul 8, 2020 at 9:56 AM Jared Smith <[email protected]> wrote:
> On Wed, Jul 8, 2020 at 8:21 AM Joshua C. Colp <[email protected]> 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
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
