On Thu, Oct 15, 2015 at 6:44 PM, Tianon Gravi <admwig...@gmail.com> wrote:
> On 13 October 2015 at 16:43, Potter, Tim (Converged Cloud) > <timothy.pot...@hpe.com> wrote: > > Hi tianon. I was curious what your plans were for uploading Go 1.5 to > unstable. Is there anything you can share? > > Go 1.5 has some minor breaking changes, so I've been waiting until I > (or some other kind soul) has had the time to do a full ratt run on Go > 1.5 and make sure all our packages either build/test successfully or > that we have a plan/patches ready to fix the issues that are bound to > come up. > FWIW, I don’t think that’s necessary for the compiler itself. Go adheres to its Go 1 stability guarantee, and any package which breaks likely did something wrong in the first place :). If this is the only thing that’s holding back the upload, I’d recommend to just go ahead with the upload. > > To Michael's point about compiling Docker via gccgo -- as the > maintainer of the build scripts for upstream, please don't do that for > anything serious. I've been working closely with IBM on that, and > none of us are really thrilled with the results so far, but it's the > only way we can get anything at all on some of their more interesting > architectures like s390x. > > ♥, > - Tianon > 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 > > _______________________________________________ > Pkg-go-maintainers mailing list > Pkg-go-maintainers@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers > -- Best regards, Michael
_______________________________________________ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
