>From the release notes, there are no intentionally breaking language changes between 1.12 and 1.13; however, 1.13 changes the behavior of tools for go modules that are provided with the default language installation that may break workflows that rely on the previous behavior.
The time required to migrate really depends on the project. go projects that depend on private modules will require a reworking of their bitbake recipe to indicate to the tools that they should not attempt to use the default module mirrors to download and authenticate the private modules. For projects that do not use private go modules, it looks like the changes to the tooling should be largely transparent, although the release notes don't 100% guarantee that. On Thu, Oct 24, 2019 at 10:07 PM Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > On Thu, 2019-10-24 at 21:59 +0430, Alexander Kube wrote: > > This patch set adds various go-1.13 recipes and changes the > > poky GOVERSION to 1.13%. It leaves the existing go-1.12 > > recipes untouched and available for existing users of > > those recipes. > > Thanks for these patches. How compatible is 1.13 with 1.12 and do we > still need the 1.12 recipes? I'm wondering how hard it will be for > people to migrate... > > Cheers, > > Richard > >
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core