On 4 March 2018 at 20:46, Otavio Salvador <[email protected]> wrote:
> I understand the need and I see the value. The GCC is harder to > upgrade but problems using newer Go toolchain does not happen very > often and likely are caused by a regression on Go itself. > > As I said, there are two options: > > a) wait for 1.10.1 release > b) keep 1.9.4 around > > My preference goes to (a) as I prefer to not include 1.10 now with > those known issues. > Considering that we're technically past the upgrade freeze and we're only still talking about this patch set as there's other, larger, patches we're holding M3 for discussing waiting for another upgrade isn't really an option unless 1.10.1 is due *very* soon. So my opinion is that as Go is getting quite some traction but is also under quite heavy development, unless there's a 1.10.1 release due *this week* which solves the problems that InfluxDB et al are having then we should ship both in this release, and drop 1.9.4 from master once 1.10.1 is added. 1.10 should be the default version, and hopefully we don't have to do this again. Ross
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
