[Openembedded-architecture] Release naming post sumo

[Scott Rifenbark]

I am hoping April 1st has something to do with this.  I can't imagine the
confusion that could arise from these three names.

Scott

On Sun, Apr 1, 2018, 10:57 AM akuster808 <akuster808 at gmail.com> wrote:

>
>
> On 04/01/2018 02:22 AM, Burton, Ross wrote:
> > On 1 April 2018 at 06:21, Richard Purdie
> > <richard.purdie at linuxfoundation.org> wrote:
> >> Following on from sumo and very in keeping with naming schemes, I'm
> >> therefore proposing we should have the "there" release. This would be
> >> followed by the "their" release and then the "theyre" release, making
> >> us really out 'there'! The latter is a bit of a compromise as I'm not
> >> sure an apostrophe would be easily handled in the branch names.
> > I know I'm sounding a bit like a scratched record, but can we try and
> > keep the names alphabetical?
> >
> > sumo -> their -> there -> theyre
>
> The concern is maintenance.  Having branches that close in name, may
> cause confusion when backport patches. Please back port to "Their" , no
> sorry, I meant There. Not Theyre..
>
> And if we verbally refer to any one of those branches, How will you know
> which on without spelling it our or defaulting to There #1, There #2, etc.
>
> - Armin
>
> >
> > Other than that, +1 from me.
> >
> > Ross
> > _______________________________________________
> > Openembedded-architecture mailing list
> > Openembedded-architecture at lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-architecture
>
>
> _______________________________________________
> Openembedded-architecture mailing list
> Openembedded-architecture at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-architecture
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-architecture/attachments/20180401/c3d05ad8/attachment-0002.html>