Thanks for filing the ticket. We we will include this change as part of mass rebuild.
If in case yo need a new side tag, please create a new ticket.
Thanks.
Metadata Update from @mohanboddu: - Issue tagged with: change-ack, changes, f32, mass rebuild
@jcajka I am only seeing golang-1.14-0.beta1.0.fc32 beta version. Can we use this for mass rebuild or is there any delay?
golang-1.14-0.beta1.0.fc32
If there is a delay, can you just use a side tag?
@mohanboddu IMO beta1 should be fine for the mass-rebuild. Google has delayed release od go1.14 for performance regression reasons in some of their large scale usages(https://github.com/golang/go/issues/36717). I have done with beta1 a scratch rebuild on my system and haven't seen any significant issues that can be attributed to the Golang itself(~10% failure rate as usual), although I have observer bit more broken deps situations(not related to the compiler). If the performance regressions show to be significant even for us(and when there will be known nature of them), I will manually rebuild affected package by hand/in side tag after mass-rebuild. Does this plan sound good to you?
@jcajka Sounds good to me. Thanks for the info.
Closing this ticket as it is included in mass rebuild.
Metadata Update from @mohanboddu: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)