<div dir="ltr">Thanks for raising this discussion, Todd!<br><br>Any input from the core team here? The Swift Android build doesn't currently work for Ubuntu 14; see <a href="https://bugs.swift.org/browse/SR-1321">https://bugs.swift.org/browse/SR-1321</a>. I'd like to know whether I should prioritize fixing this, or whether I should focus on getting the build ready for Ubuntu 16.<div><br></div><div>- Brian Gesiak</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 26, 2016 at 10:57 AM, Todd Fiala via swift-dev <span dir="ltr"><<a href="mailto:swift-dev@swift.org" target="_blank">swift-dev@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Thanks, Ryan. Yes, the intent was to harmonize with the Ubuntu release philosophy.<div><br></div><div>I haven’t heard any opposition to this plan. I’m going to move forward with resourcing and executing on this plan. More communication to follow once those details are worked out.</div><div><br></div><div>Thanks, all!</div><div><br></div><div>Sincerely,</div><div>Todd Fiala</div><div><div class="h5"><div><br><div><blockquote type="cite"><div>On Apr 26, 2016, at 6:24 AM, Ryan Lovelett via swift-lldb-dev <<a href="mailto:swift-lldb-dev@swift.org" target="_blank">swift-lldb-dev@swift.org</a>> wrote:</div><br><div>
<div><div>On Thu, Apr 21, 2016, at 01:12 PM, Todd Fiala via swift-lldb-dev wrote:<br></div>
<blockquote type="cite"><div dir="ltr"><p><span>Hi all,</span><br></p><p>I wanted to propose how we can go about handling newer Ubuntu releases in a systematic way. This covers how we handle Ubuntu on our CI, but also reflects where we'll be focusing effort at any given point. The primary intent is to support the most recent Ubuntu Long Term Service release and the absolute latest Ubuntu release, with a bit of overlap when phasing out the LTS release that is going out of scope.<span></span><br></p><p>Since the next release, fast moving or not, is the next Long Term Stability release, Ubuntu 16.04 LTS (available now), I propose we:<br></p><p><span>* swap out our 15.10 fast moving release with Ubuntu 16.04 LTS.</span><br></p><p><span>* allow 16.04 and 14.04 to co-exist to give our stability-minded community time to switch over to 16.04.</span><br></p><p>When 16.10 comes out in October 2016, we drop 14.04 and move 16.10 onto those builders.<span></span><br></p><p>This continues to have us testing against the latest release, which will be Ubuntu 16.04 LTS when we switch, gives us the latest stable coverage (also 16.04), and gives our community a little more time with active coverage on 14.04, the previous long term support version. We’ll then get back to the normal program in October 2016 when we pick up the latest fast-moving release, with coverage on Ubuntu 16.10 and Ubuntu 16.04 LTS.<span></span><br></p><p>This assumes we want to keep our eyes on no more than two Ubuntu releases at a time, which matches current CI infrastructure planning.<span></span><br></p><p>Looking forward over the next two years, this is the schedule I’m proposing:<span></span><br></p><p><br></p><ul><li>April 2016:<span> </span><span> </span>Replace Ubuntu 15.10 with Ubuntu 16.04 (coverage: Ubuntu 14.04, Ubuntu 16.04 LTS)<br></li><li>October 2016:<span> </span><span> </span>Replace Ubuntu 14.04 with Ubuntu 16.10 (coverage: Ubuntu 16.04 LTS, Ubuntu 16.10)<br></li><li>April 2017:<span> </span><span> </span>Replace Ubuntu 16.10 with Ubuntu 17.04 (coverage: Ubuntu 16.04 LTS, Ubuntu 17.04)<br></li><li>October 2017:<span> </span><span> </span>Replace Ubuntu 17.04 with Ubuntu 17.10 (coverage: Ubuntu 16.04 LTS, Ubuntu 17.10)<br></li><li>April 2018:<span> </span><span> </span>Replace Ubuntu 17.10 with Ubuntu 18.04 LTS (coverage: Ubuntu 16.04, Ubuntu 18.04 LTS)<br></li></ul><p><br></p><p>Thoughts? Once we finalize the plan, I'll coordinate with the infrastructure teams and round up resources needed to get Ubuntu 16.04 supported and on the CI.<br></p></div>
</blockquote><div> </div>
<div>This seems to mostly match up with the guidance provided by Canonical and the community around Ubuntu. Therefore it seems reasonable to me.<br></div>
<div> </div>
<div>I like it. Consider this a vote in favor.<br></div>
<div> </div>
<blockquote type="cite"><div dir="ltr"><p>Thanks!<span></span><br></p><div>Sincerely,<br></div>
<div>Todd Fiala<br></div>
</div>
<div><u>_______________________________________________</u><br></div>
<div>swift-lldb-dev mailing list<br></div>
<div><a href="mailto:swift-lldb-dev@swift.org" target="_blank">swift-lldb-dev@swift.org</a><br></div>
<div><a href="https://lists.swift.org/mailman/listinfo/swift-lldb-dev" target="_blank">https://lists.swift.org/mailman/listinfo/swift-lldb-dev</a><br></div>
</blockquote><div> </div>
</div>
_______________________________________________<br>swift-lldb-dev mailing list<br><a href="mailto:swift-lldb-dev@swift.org" target="_blank">swift-lldb-dev@swift.org</a><br><a href="https://lists.swift.org/mailman/listinfo/swift-lldb-dev" target="_blank">https://lists.swift.org/mailman/listinfo/swift-lldb-dev</a><br></div></blockquote></div><br></div></div></div></div><br>_______________________________________________<br>
swift-dev mailing list<br>
<a href="mailto:swift-dev@swift.org">swift-dev@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-dev" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-dev</a><br>
<br></blockquote></div><br></div>