<div dir="ltr">I tend to agree, although i am curious to hear what others think.<div>My hope would be that we'd be balanced about adopting "new language variants and dependencies" - if we have reasons to do so, then do those outweigh stagnating for the sake of being able to build on older ubuntu stables?</div><div><br></div><div>br,kg</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 6, 2015 at 10:35 PM, Daniel van Vugt <span dir="ltr"><<a href="mailto:daniel.van.vugt@canonical.com" target="_blank">daniel.van.vugt@canonical.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">All,<br>
<br>
In the past we've made decisions to adopt new language variants and dependencies for Mir that meant only users on the latest Ubuntu release could build the latest Mir code. And if the latest Ubuntu release means the pre-release then we're probably excluding most Ubuntu users from being able to build the Mir code and getting involved.<br>
<br>
In early development that's fine, but I'm wondering if we can agree to aim for some solidification. For example, should we say that after Ubuntu 16.04 LTS is released all Ubuntu releases thereafter should be usable for doing development on Mir? Or just the latest LTS plus the latest release (ie. follow the Ubuntu support schedule)?<span class="HOEnZb"><font color="#888888"><br>
<br>
- Daniel<br>
<br>
-- <br>
Mir-devel mailing list<br>
<a href="mailto:Mir-devel@lists.ubuntu.com" target="_blank">Mir-devel@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/mir-devel" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailman/listinfo/mir-devel</a><br>
</font></span></blockquote></div><br></div>