<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">I think this best describes the issue:</div><div class=""><a href="https://www.youtube.com/watch?v=zsKOYQ7z9CE" class="">https://www.youtube.com/watch?v=zsKOYQ7z9CE</a></div><div class=""><br class=""></div><div class=""><div class="">
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On 26 Sep 2020, at 9:17 am, Benjamin Kaduk <<a href="mailto:kaduk@mit.edu" class="">kaduk@mit.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Thu, Sep 24, 2020 at 12:33:56PM +1000, Dr Paul Dale wrote:<br class=""><blockquote type="cite" class="">I’m seeing quite a bit of activity going on which isn’t related to the 3.0beta1 milestone.<br class="">We’re well past the cutoff date announced for new features in the code.<br class=""><br class="">Should we be limiting the “new” stuff going in?<br class=""><br class="">I’m fine with bug fixes, they make sense. I’m fine with the list of beta1 pull requests continuing.<br class="">It’s the rest that is more concerning.<br class=""><br class="">Does anyone else have a similar view?<br class=""></blockquote><br class="">I think we should probably avoid putting in large or potentially<br class="">destabilizing changes, but don't see much reason to put a total freeze in<br class="">place (even with your listed exceptions).<br class=""><br class="">-Ben<br class=""></div></div></blockquote></div><br class=""></div></body></html>