Revision as of 09:46, 31 December 2019

Golang 1.14

Summary

Rebase of Golang package to upcoming version 1.14 in Fedora 32, including rebuild of all dependent packages(pre-release version of Go will be used for rebuild, if released version will not be available at the time of the mass rebuild).

Owner

Name: Jakub Čajka
Email: jcajka@redhat.com
Release notes ticket:

Current status

Targeted release: Fedora 32
Last updated: 2019-12-31
Tracker bug:
Release Notes tracking:

Detailed Description

Rebase of Golang package to upcoming version 1.14 in Fedora 32. Golang 1.14 is schedule to be released in Feb 2020. Due to current nature and state of Go packages, rebuild of dependent package will be required to pick up the changes.

Benefit to Fedora

Staying closely behind upstream by providing latest release of golang, which includes performance improvements and improvements in support for currently supported platforms among other bug fixes and new features. For complete list of changes see upstream change notes at https://tip.golang.org/doc/go1.14 . In result Fedora will be providing solid development platform for Go language.

Scope

Proposal owners: Rebase golang package in f32, help with resolving possible issues found during package rebuilds.

Other developers: Fix possible issues, with help from golang maintainers.

Release engineering: Rebuild of dependent packages as part of planned mass-rebuild. Tracking ticket https://pagure.io/releng/issue/9136
- List of deliverables: N/A

Policies and guidelines: N/A

Trademark approval: N/A

Upgrade/compatibility impact

None

How To Test

0.: a)Install golang 1.14 from rawhide and use it to build your application(s)/package(s).; b)Scratch build against rawhide.
1.: Your application/package built using golang 1.14 should work as expected.

User Experience

None

Dependencies

dnf repoquery -q  --releasever=rawhide --disablerepo='*' --qf='%{name}' --enablerepo=fedora-source --enablerepo=updates-source --enablerepo=updates-testing-source --archlist=src --whatrequires 'golang'
dnf repoquery -q  --releasever=rawhide --disablerepo='*' --qf='%{name}' --enablerepo=fedora-source --enablerepo=updates-source --enablerepo=updates-testing-source --archlist=src --whatrequires 'compiler(go-compiler)'
dnf repoquery -q  --releasever=rawhide --disablerepo='*' --qf='%{name}' --enablerepo=fedora-source --enablerepo=updates-source --enablerepo=updates-testing-source --archlist=src --whatrequires 'compiler(golang)'

Not all of listed require re-build as they might not ship binaries and/or do not use golang compiler during build, but only use Go rpm macros that pull it in to every build root.

Contingency Plan

Contingency mechanism:Reverting to golang version 1.13.X if significatnt issues are discovered.
Contingency deadline: Beta Freeze(?)
Blocks release? No
Blocks product? No

Documentation

https://tip.golang.org/doc/go1.14

Release Notes

Release Notes tracking: []

@@ Line 76: / Line 76: @@
 <!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
-* Release engineering: Rebuild of dependent packages as part of planned mass-rebuild. Tracking ticket TBD <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Release engineering: Rebuild of dependent packages as part of planned mass-rebuild. Tracking ticket https://pagure.io/releng/issue/9136 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.
 Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.-->

Search

Changes/golang1.14: Difference between revisions