- [ANNOUNCEMENT] Yocto Project 3.3.1 (hardknott-25.0.1) is Released
Re: [ANNOUNCEMENT] Yocto Project 3.3.1 (hardknott-25.0.1) is Released
toggle quoted messageShow quoted text
After discussing it we've gone ahead and deleted the hardknott-25.0.0 tag then added hardknott-3.3, and hardknott-3.3.1 tags.
From now on any release before 3.3 will have the poky version number tags and from the 3.3 release forward we will use branchname-yocto-version tags.
> -----Original Message-----
> From: Richard Purdie <richard.purdie@...>
> Sent: den 25 maj 2021 14:44
> To: Peter Kjellerstedt <peter.kjellerstedt@...>; Vineela
> Cc: 'yocto@...' <yocto@...>; Michael
> Halstead <mhalstead@...>
> Subject: Re: [yocto] [ANNOUNCEMENT] Yocto Project 3.3.1 (hardknott-25.0.1)
> is Released
> On Tue, 2021-05-25 at 12:13 +0000, Peter Kjellerstedt wrote:
> > It seems the ”hardknott-25.0.1” tag is missing for meta-gplv2.
> > The “yoccto-3.3.1” tag is present.
> This was deliberate since we've been trying to step away from the
> "poky" version numbers, I'm not sure they add much to anything.
> Is there a particular reason you were looking for those?
Well, those are the ones we have traditionally been using. The benefit I see
with them are that they contain the release name. For me as a user, it is much
easier to see and refer to "hardknott-something.1" than "yocto-3.3.1". I.e.,
I don't have a relation to the "25.0" or "3.3" part, but to the release name.
We typically only talk about "hardknott" or "the second hardknott release".
That said, a tag such as "yocto-hardknott-3.3.1" or "hardknott-3.3.1" would
fulfill the same properties as "hardknott-25.0.1", though the one without
the "yocto-" prefix is more suitable when tab completing, e.g.,
`git log hardknott-3.3..hardknott-3.3.1`, so that is the one I would use if
it was up to me. ;)
Linux Foundation / Yocto Project
Systems Operations Engineer
Join email@example.com to automatically receive all group messages.