On Fri, Aug 20, 2021 at 9:34 AM Alexander Kanavin
wrote:
>
> Maybe we should go straight to 1.17?
>
Eventually yes, but for backport reasons lets fist move to latest on
1.16 release and then go to 1.17
so we can backport easily to releases.
> Alex
>
> On Fri, 20 Aug 2021 at 17:39, Sakib Sajal w
On 2021-08-20 2:41 p.m., Sakib Sajal wrote:
On 2021-08-20 12:34 p.m., Alexander Kanavin wrote:
**[Please note: This e-mail is from an EXTERNAL e-mail address]
Maybe we should go straight to 1.17?
Sure for master but on hardknott probably not!!
That's not our typical approach for GAed relea
On 2021-08-20 12:34 p.m., Alexander Kanavin wrote:
**[Please note: This e-mail is from an EXTERNAL e-mail address]
Maybe we should go straight to 1.17?
I was thinking the same, but stuck with 1.16 release for hardknott and
not bump the minor version.
I am working on upgrading the recipe on
Maybe we should go straight to 1.17?
Alex
On Fri, 20 Aug 2021 at 17:39, Sakib Sajal wrote:
> Signed-off-by: Sakib Sajal
> ---
> meta/recipes-devtools/go/{go-1.16.5.inc => go-1.16.7.inc} | 4 ++--
> ...{go-binary-native_1.16.5.bb => go-binary-native_1.16.7.bb} | 4 ++--
> ...o-cross-canadi
Signed-off-by: Sakib Sajal
---
meta/recipes-devtools/go/{go-1.16.5.inc => go-1.16.7.inc} | 4 ++--
...{go-binary-native_1.16.5.bb => go-binary-native_1.16.7.bb} | 4 ++--
...o-cross-canadian_1.16.5.bb => go-cross-canadian_1.16.7.bb} | 0
.../go/{go-cross_1.16.5.bb => go-cross_1.16.7.bb}
