<div dir="ltr">Thank you for this great plan.<div><br></div><div>Sounds good to me :).</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Apr 1, 2018 at 7:21 AM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Naming is always a tricky subject and I've been told we've had some<br>
'out there' names for releases. I have tried to make things<br>
alphabetical recently to help people understand the order of the<br>
releases. In the past I've also agreed to announce the release names<br>
earlier to better aid people in planning for the new releases. <br>
<br>
There have been calls to extend this to further release names,<br>
particularly with some of the longer term planning initiatives being<br>
discussed and I've therefore decided to try and assist this and annouce<br>
a little further ahead.<br>
<br>
Following on from sumo and very in keeping with naming schemes, I'm<br>
therefore proposing we should have the "there" release. This would be<br>
followed by the "their" release and then the "theyre" release, making<br>
us really out 'there'! The latter is a bit of a compromise as I'm not<br>
sure an apostrophe would be easily handled in the branch names.<br>
<br>
Special thanks to Michael for help when brainstorming on a new scheme<br>
over pizza recently!<br>
<br>
Cheers,<br>
<br>
Richard<br>
<br>
<br>
______________________________<wbr>_________________<br>
Openembedded-architecture mailing list<br>
<a href="mailto:Openembedded-architecture@lists.openembedded.org">Openembedded-architecture@<wbr>lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-architecture" rel="noreferrer" target="_blank">http://lists.openembedded.org/<wbr>mailman/listinfo/openembedded-<wbr>architecture</a><br>
</blockquote></div><br></div>