[OE-core] OpenEmbedded TSC Meeting Minutes 2019-10-21

[Khem Raj]

On Fri, Oct 25, 2019 at 4:21 PM Martin Jansa <martin.jansa at gmail.com> wrote:

> On Tue, Oct 22, 2019 at 03:58:01PM +1300, Paul Eggleton wrote:
> > OpenEmbedded Technical Steering Committee (TSC) Meeting Minutes
> 2019-10-21
> >
> ==========================================================================
> >
> > Meeting was held in #oe-tsc on Freenode; channel access public.
> >
> > Present:
> > - Richard Purdie (RP)
> > - Joshua Watt (JPEW)
> > - Martin Jansa (JaMa)
> > - Bruce Ashfield (zeddii)
> > - Paul Eggleton (bluelightning)
> >
> > Summary:
> > - yocto-X.Y tags will be added to the bitbake and openembedded-core
> repos (after the upcoming 3.0 release) to make release revisions easier to
> find
> > - YYYY-MM.X-CODENAME tags will replace YYYY-MM tags going forward in the
> openembedded-core repo (again, after the 3.0 release)
>
> I don't have permissions to push the tags directly to git.oe.org:
>
> openembedded-core $ git push origin yocto-3.0
> fatal: remote error: access denied or repository not exported:
> /openembedded-core
>
> I've pushed new and missing tags to github (since 1.8 fido), you can just
> re-push them to
> git.oe.org with:
>
> OE_TAGS="2019-10-zeus yocto-3.0 \
>          2019-04-warrior yocto-2.7 \
>          2018-10-thud yocto-2.6 \
>          2018-04-sumo yocto-2.5 \
>          2017-10-rocko yocto-2.4 \
>          2017-04 2017-04-pyro yocto-2.3 \
>          2016-10-morty yocto-2.2 \
>          2016-04-krogoth yocto-2.1 \
>          2015-10 2015-10-jethro yocto-2.0 \
>          2015-04-fido yocto-1.8"
>
> BB_TAGS="2019-10-zeus yocto-3.0 \
>          2019-04-warrior yocto-2.7 \
>          2018-10-thud yocto-2.6 \
>          2018-04-sumo yocto-2.5 \
>          1.36.0 2017-10-rocko yocto-2.4 \
>          1.34.0 2017-04-pyro yocto-2.3 \
>          1.32.0 2016-10-morty yocto-2.2 \
>          1.30.0 2016-04-krogoth yocto-2.1 \
>          1.28.0 2015-10-jethro yocto-2.0 \
>          2015-04-fido yocto-1.8"
>
> cd openembedded-core
> git remote add shr https://github.com/shr-distribution/oe-core.git
> git fetch --tags shr
> git push origin $OE_TAGS
> git remote rm shr
> cd ..
>
> cd bitbake
> git remote add shr https://github.com/shr-distribution/bitbake.git
> git fetch --tags shr
> git push origin $BB_TAGS
> git remote rm shr
>
> I wonder if we should start tagging something in meta-oe repo as well (to
> have similar
> tag names in all active repos from https://git.openembedded.org), but for
> meta-oe it's
> difficult to decide which commits to tag as there are no official releases
> nor references
> from Yocto release or poky repo. So maybe YYYY-MM-CODENAME 2019-10-zeus
> and newer?
> Tags yocto-X.Y don't make sense in meta-oe repo, right?


Tags only make sense if they are validated together or something which we
don’t do for meta-openembedded so it will not have that expectation met
where as it might have it with all repos that yocto project reference
distro  currently tests

I see it conveys some good info about codename -> release number -> time of
year which is confusing at times

Perhaps thinking about this to be consistent might serve us well



>
> Cheers,
> --
> _______________________________________________
> tsc mailing list
> tsc at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/tsc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/tsc/attachments/20191025/8fb3b365/attachment-0003.html>