<div dir="ltr">On 19 March 2018 at 19:22, akuster808 <span dir="ltr"><<a href="mailto:akuster808@gmail.com" target="_blank">akuster808@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><span class="">
<blockquote type="cite"><div class="m_-7367521829909012032WordSection1"><p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial",sans-serif;color:black">YP
2.5 M3 is in feature freeze. See status above.</span></p>
</div>
</blockquote></span>
Does this include package updates? <br></div></blockquote><div><br></div><div>Yes, upgrades count as features.</div><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">
Do we have a place identified for new changes (2.6) while 2.5
stabilizes. <br></div></blockquote><div><br></div><div>A formal place, no. I tend to queue stuff in a branch if master isn't taking all of my energy, otherwise the patches will sit on the list until 2.5 releases. Typically master and sumo branches won't diverge until post-release.</div><div><br></div><div>Ross </div></div></div></div>