<div dir="ltr">From the release notes, there are no intentionally breaking <div>language changes between 1.12 and 1.13; however, 1.13 </div><div>changes the behavior of tools for go modules that are </div><div>provided with the default language installation that may </div><div>break workflows that rely on the previous behavior.</div><div><br></div><div>The time required to migrate really depends on the project. </div><div>go projects that depend on private modules will require a </div><div>reworking of their bitbake recipe to indicate to the tools that </div><div>they should not attempt to use the default module mirrors to </div><div>download and authenticate the private modules.</div><div><br></div><div>For projects that do not use private go modules, it looks like</div><div> the changes to the tooling should be largely transparent, </div><div>although the release notes don't 100% guarantee that.</div><div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Oct 24, 2019 at 10:07 PM Richard Purdie <<a href="mailto:richard.purdie@linuxfoundation.org">richard.purdie@linuxfoundation.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Thu, 2019-10-24 at 21:59 +0430, Alexander Kube wrote:<br>
> This patch set adds various go-1.13 recipes and changes the<br>
> poky GOVERSION to 1.13%. It leaves the existing go-1.12<br>
> recipes untouched and available for existing users of<br>
> those recipes.<br>
<br>
Thanks for these patches. How compatible is 1.13 with 1.12 and do we<br>
still need the 1.12 recipes? I'm wondering how hard it will be for<br>
people to migrate...<br>
<br>
Cheers,<br>
<br>
Richard<br>
<br>
</blockquote></div>