[Openembedded-architecture] Notes from the OEDAM "Naming Table"

Richard Purdie richard.purdie at linuxfoundation.org
Tue Sep 27 14:26:00 UTC 2016


On Mon, 2016-09-05 at 13:16 +0200, Martin Jansa wrote:
> On Sat, Sep 03, 2016 at 12:04:26PM +0100, Richard Purdie wrote:
> > On Sat, 2016-09-03 at 12:14 +0200, Martin Jansa wrote:
> > > My only 3 "naming" issues are:
> > > 1) The next release codename is decided only shortly before the
> > > actual release When I need to talk with management about plans
> > > for upgrading our builds to Yocto 2.2 release I'll probably
> > > reference it as "Yocto 2.2 (master)" while other releases are
> > > referenced as Yocto x.x (codename) - even worse when some
> > > internal things still have reference to "Yocto 1.7 (master)",
> > > because they were created before Dizzy was released
> > > and cannot be updated later.
> > > So in some parts it's easier to use numbers which should be known
> > > in advance (darn that mysterious 1.9 release which is still
> > > referenced internally and also on Yocto Project wiki pages).
> > > Knowing the codename of next release in advance (announced
> > > together with current release) would be very helpful for us.
> > This is good feedback. I'd not considered it in those terms and
> > there is no reason we can't announce the release names further in
> > advance. I will admit I haven't actually decided on what 2.2 will
> > be called but that doesn't mean I can't get a move on with these!
> > :)

Sorry, I'd forgotten to get back to this. 2.2 will be known as "morty".
2.3 will be known as "pyro".

Cheers,

Richard






More information about the Openembedded-architecture mailing list