[almighty] Upgrading to go 1.7.3

[Karanbir Singh]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 25/11/16 06:37, Baiju Muthukadan wrote:
> Hi KB,
> 
> Even though we don't need Go 1.7 immediately. Is there any plan to 
> update the version to 1.7? What are the key requirements to update
> to a newer version?

1) to actually have a requirement to upgrade
2) a managed path for golang itself.

we can get creative with (2) for the time being and in the short term,
but as we move into the next few sprints, I will ask everyone to make
sure they dont have open ended deps in the toolchains above the platform
.

You dont want to get stuck in a situation where an upstream update or
a dep change forces the project off the rails.

> Do we need RPMs available in CentOS repository? Is availability in
> EPEL repo is sufficient?

since golang is in the distro - it will never show up in EPEL.

Regards,

- -- 
Karanbir Singh, Project Lead, The CentOS Project, London, UK
Red Hat Ext. 8274455 | DID: 0044 207 009 4455
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJYOCqJAAoJEI3Oi2Mx7xbtZDMIAKbEYa28CmpvYFqLUrw3oufF
HIhp46F02TZqNXa7/7QBtARrtLkJu0xR5f8q57KpGgjLIyTBVBsGivZPr48JhX/x
sp3nj9RDF/YGtWdYDcdO5nTg+Q4lbwjN1STEKNKCbKWRhN2htJtJXBAWeQO4CyG3
3o6rKUPONmRpyJQ2c2WNj2Vk5FuVk5oM0ZMK0UdcqwgkUGVdQz0ijOAhbI5UZXrM
bnM38PDxJJ5gnKywBsG0r0CYQNt85UoANn6h2ulPk/qCfPtpzGSS+4LtMzl01Pw4
Fv5hFsmfHy0f53xn3DJfTbz4ZD+MN6YQFwFgvMXvxtISTQ/prjGNi5bqo+YnNd0=
=2gfE
-----END PGP SIGNATURE-----