<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 10pt; color: #000000"><div></div><div data-marker="__SIG_PRE__"></div><div><span id="zwchr" data-marker="__DIVIDER__">----- On Jul 8, 2020, at 8:20 AM, Joshua C. Colp <jcolp@sangoma.com> wrote:</span></div><div data-marker="__QUOTED_TEXT__"><blockquote style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;" data-mce-style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><div dir="ltr"><div>I'd like to propose that instead of cutting the 18.0 branch on July 15th we simply cut the 18 branch, and that it continues to receive all bug fixes. Approximately a month before a target release of 18.0.0 we create the first release candidate, 18.0.0-rc1. At this time we also create release candidates of the other branches. All release candidates will then be left available for a prolonged period of time to give people ample time to test. On the release date all will be released, ensuring that all branches including 18 have the same set of bug fixes as appropriate to their version.</div><br><div>This removes the confusion for developers over whether to include a fix, since the 18.0 branch won't exist until rc1 at which point normal cherry pick rules apply. This also eliminates the confusion experienced by users since all releases will be on the same page at the same time at release.</div><br><div>What do people think? Do we believe that a month out is ample enough? The 18 branch itself will exist, so that can be used for early testing (and likely will be). If a month isn't enough it could be moved out further. Really I think thanks to the testing that happens and the code review I don't think we need as long of a stabilization period as has been needed in the past, so this helps shrink it.</div></div></blockquote><div>The proposal sounds very reasonable. Yes, with all the testing that is in the project now, a month should be good enough.</div><div><br data-mce-bogus="1"></div><div>--</div><div>Michael L. Young</div><div>(elguero)</div></div></div></body></html>