<div dir="ltr">On 20 March 2018 at 10:07, Alexander Kanavin <span dir="ltr"><<a href="mailto:alexander.kanavin@linux.intel.com" target="_blank">alexander.kanavin@linux.intel.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"><span class="">On 03/19/2018 10:07 PM, Burton, Ross wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  Do we have a place identified for new changes (2.6) while 2.5<br>
  stabilizes.<br>
<br>
<br>
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.<br>
</blockquote>
<br></span>
Which brings me to a question: what is a good schedule and cadence for AUH runs? Currently it's run on the 15th of every odd-numbered month (so January, March, and so on), but I thought of shifting it one month forward, so it doesn't land right in the middle of a feature freeze. Thoughts?<br></blockquote><div><br></div><div>How long does a single run take, and why not run it every month?</div><div><br></div><div>Ross </div></div></div></div>