Re: Go 1.3 is unmaintained/unsupported upstream
On 02/13/2015 05:26 PM, John Lenton wrote: Go 1.3.3, which we are shipping in Vivid, is unmaintained upstream¹ (yes, despite being released less than six months ago). Would it be possible to move to 1.4 in vivid? This wouldn't fix the fact that it will become unmaintained in Vivid's timeframe, but at least we can get the bugs we find during development fixed upstream. just use gccgo everywhere, which is go 1.4. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Go 1.3 is unmaintained/unsupported upstream
Robie Basak [2015-02-13 17:39 +]: But this is the way the world is going, and something I think Ubuntu needs to adapt to. I heavily disagree for something as fundamental as a toolchain/compiler, but we've had this conversation a lot of times already :) I'm not sure how, though. In theory, if their quality is good, could we SRU and rely on their backward compatibility guarantee? It's great to hear that there now is some effort to maintain backwards compatibility. When we started to adopt Go, there wasn't even that, but it was still in the early stage of anything goes. If there is some enforced backwards compatibility now, it does sound prudent to re-discuss the maintenance/upgrades indeed. Would we really need to rebuild all reverse dependencies? If we'd update Go in a stable release, then we must make sure that all reverse dependencies are still *buildable* and still work without a regression. IMHO they don't actually need to be rebuilt as SRUs too in the sense of doing 70 no-change uploads. We'd only need to upload those reverse deps which need sourceful changes to build and/or work with a new Go compiler (and then need to have an SRU exception for this). Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Go 1.3 is unmaintained/unsupported upstream
On Saturday, February 14, 2015 05:00:29 PM Martin Pitt wrote: Robie Basak [2015-02-13 17:39 +]: But this is the way the world is going, and something I think Ubuntu needs to adapt to. I heavily disagree for something as fundamental as a toolchain/compiler, but we've had this conversation a lot of times already :) I'm not sure how, though. In theory, if their quality is good, could we SRU and rely on their backward compatibility guarantee? It's great to hear that there now is some effort to maintain backwards compatibility. When we started to adopt Go, there wasn't even that, but it was still in the early stage of anything goes. If there is some enforced backwards compatibility now, it does sound prudent to re-discuss the maintenance/upgrades indeed. Would we really need to rebuild all reverse dependencies? If we'd update Go in a stable release, then we must make sure that all reverse dependencies are still *buildable* and still work without a regression. IMHO they don't actually need to be rebuilt as SRUs too in the sense of doing 70 no-change uploads. We'd only need to upload those reverse deps which need sourceful changes to build and/or work with a new Go compiler (and then need to have an SRU exception for this). Before libclamav stabilized, we had to do things similar to this. We not only rebuilt them, but also tested they still worked (at least lightly). That was part of the TB approved conditions for the SRU exception. It takes a lot of work, but we have established for a somewhat similar situation it can be done and successfully mitigate SRU regression risks. Scott K -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Go 1.3 is unmaintained/unsupported upstream
Go 1.3.3, which we are shipping in Vivid, is unmaintained upstream¹ (yes, despite being released less than six months ago). Would it be possible to move to 1.4 in vivid? This wouldn't fix the fact that it will become unmaintained in Vivid's timeframe, but at least we can get the bugs we find during development fixed upstream. 1. https://github.com/golang/go/issues/9866#event-235479734 -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Go 1.3 is unmaintained/unsupported upstream
El 13/02/15 a las 13:26, John Lenton escibió: Go 1.3.3, which we are shipping in Vivid, is unmaintained upstream¹ (yes, despite being released less than six months ago). Would it be possible to move to 1.4 in vivid? This wouldn't fix the fact that it will become unmaintained in Vivid's timeframe, but at least we can get the bugs we find during development fixed upstream. 1. https://github.com/golang/go/issues/9866#event-235479734 If I do not misunderstand , with ubuntu Makeyou can install the latest version http://blog.didrocks.fr/post/Ubuntu-Make-0.4-starts-the-new-year-adding-Go-support -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Go 1.3 is unmaintained/unsupported upstream
On Friday, February 13, 2015 18:17:29 Martin Pitt wrote: John Lenton [2015-02-13 16:26 +]: Go 1.3.3, which we are shipping in Vivid, is unmaintained upstream¹ (yes, despite being released less than six months ago). Would it be possible to move to 1.4 in vivid? Better be quick, feature freeze is next Thursday :-) If you prepare/upload a package and ensure that all packages that build-depend on it are still working (we have 76: reverse-depends -b src:golang), it should be fine. I suggest staging that in a PPA, and once everything builds, upload the new golang-go, and any package which needs updates to build with 1.4. This wouldn't fix the fact that it will become unmaintained in Vivid's timeframe It's in universe, so inherently unsupported, and I figure at the moment folks developing with Go would rather use some backports or a PPA anyway? Perhaps Go and the redepends should be removed from the archive then? Scott K -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Go 1.3 is unmaintained/unsupported upstream
On Fri, Feb 13, 2015 at 12:27:14PM -0500, Scott Kitterman wrote: Perhaps Go and the redepends should be removed from the archive then? There does seem to be a fundamental dissonance between upstream's policy and Ubuntu's policies here. With upstream not maintaining bugfix only branches; instead only maintaining a feature branch that retains a backwards compatibility guarantee. And Ubuntu's SRU policy preventing us from updating our stable releases this way by default. But this is the way the world is going, and something I think Ubuntu needs to adapt to. I'm not sure how, though. In theory, if their quality is good, could we SRU and rely on their backward compatibility guarantee? Would we really need to rebuild all reverse dependencies? Or are they ABI compatible too? Something for the TB to consider I guess. signature.asc Description: Digital signature -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Go 1.3 is unmaintained/unsupported upstream
John Lenton [2015-02-13 16:26 +]: Go 1.3.3, which we are shipping in Vivid, is unmaintained upstream¹ (yes, despite being released less than six months ago). Would it be possible to move to 1.4 in vivid? Better be quick, feature freeze is next Thursday :-) If you prepare/upload a package and ensure that all packages that build-depend on it are still working (we have 76: reverse-depends -b src:golang), it should be fine. I suggest staging that in a PPA, and once everything builds, upload the new golang-go, and any package which needs updates to build with 1.4. This wouldn't fix the fact that it will become unmaintained in Vivid's timeframe It's in universe, so inherently unsupported, and I figure at the moment folks developing with Go would rather use some backports or a PPA anyway? Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
