<div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Oct 25, 2019 at 4:21 PM Martin Jansa <<a href="mailto:martin.jansa@gmail.com">martin.jansa@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, Oct 22, 2019 at 03:58:01PM +1300, Paul Eggleton wrote:<br>
> OpenEmbedded Technical Steering Committee (TSC) Meeting Minutes 2019-10-21<br>
> ==========================================================================<br>
> <br>
> Meeting was held in #oe-tsc on Freenode; channel access public.<br>
> <br>
> Present:<br>
> - Richard Purdie (RP)<br>
> - Joshua Watt (JPEW)<br>
> - Martin Jansa (JaMa)<br>
> - Bruce Ashfield (zeddii)<br>
> - Paul Eggleton (bluelightning)<br>
> <br>
> Summary:<br>
> - 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<br>
> - YYYY-MM.X-CODENAME tags will replace YYYY-MM tags going forward in the openembedded-core repo (again, after the 3.0 release)<br>
<br>
I don't have permissions to push the tags directly to <a href="http://git.oe.org" rel="noreferrer" target="_blank">git.oe.org</a>:<br>
<br>
openembedded-core $ git push origin yocto-3.0<br>
fatal: remote error: access denied or repository not exported: /openembedded-core<br>
<br>
I've pushed new and missing tags to github (since 1.8 fido), you can just re-push them to<br>
<a href="http://git.oe.org" rel="noreferrer" target="_blank">git.oe.org</a> with:<br>
<br>
OE_TAGS="2019-10-zeus yocto-3.0 \<br>
2019-04-warrior yocto-2.7 \<br>
2018-10-thud yocto-2.6 \<br>
2018-04-sumo yocto-2.5 \<br>
2017-10-rocko yocto-2.4 \<br>
2017-04 2017-04-pyro yocto-2.3 \<br>
2016-10-morty yocto-2.2 \<br>
2016-04-krogoth yocto-2.1 \<br>
2015-10 2015-10-jethro yocto-2.0 \<br>
2015-04-fido yocto-1.8"<br>
<br>
BB_TAGS="2019-10-zeus yocto-3.0 \<br>
2019-04-warrior yocto-2.7 \<br>
2018-10-thud yocto-2.6 \<br>
2018-04-sumo yocto-2.5 \<br>
1.36.0 2017-10-rocko yocto-2.4 \<br>
1.34.0 2017-04-pyro yocto-2.3 \<br>
1.32.0 2016-10-morty yocto-2.2 \<br>
1.30.0 2016-04-krogoth yocto-2.1 \<br>
1.28.0 2015-10-jethro yocto-2.0 \<br>
2015-04-fido yocto-1.8"<br>
<br>
cd openembedded-core<br>
git remote add shr <a href="https://github.com/shr-distribution/oe-core.git" rel="noreferrer" target="_blank">https://github.com/shr-distribution/oe-core.git</a><br>
git fetch --tags shr<br>
git push origin $OE_TAGS<br>
git remote rm shr<br>
cd ..<br>
<br>
cd bitbake<br>
git remote add shr <a href="https://github.com/shr-distribution/bitbake.git" rel="noreferrer" target="_blank">https://github.com/shr-distribution/bitbake.git</a><br>
git fetch --tags shr<br>
git push origin $BB_TAGS<br>
git remote rm shr<br>
<br>
I wonder if we should start tagging something in meta-oe repo as well (to have similar<br>
tag names in all active repos from <a href="https://git.openembedded.org" rel="noreferrer" target="_blank">https://git.openembedded.org</a>), but for meta-oe it's<br>
difficult to decide which commits to tag as there are no official releases nor references<br>
from Yocto release or poky repo. So maybe YYYY-MM-CODENAME 2019-10-zeus and newer?<br>
Tags yocto-X.Y don't make sense in meta-oe repo, right?</blockquote><div dir="auto"><br></div><div dir="auto">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 </div><div dir="auto"><br></div><div dir="auto">I see it conveys some good info about codename -> release number -> time of year which is confusing at times </div><div dir="auto"><br></div><div dir="auto">Perhaps thinking about this to be consistent might serve us well </div><div dir="auto"><br></div><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
Cheers,<br>
-- <br>
_______________________________________________<br>
tsc mailing list<br>
<a href="mailto:tsc@lists.openembedded.org" target="_blank">tsc@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/tsc" rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/tsc</a><br>
</blockquote></div></div>