It does break the API, as evinced by one build failure. I’m not aware of situations in the past where we created a new binary. How would we name them? Is it worth the trouble?
Personally, I would just update the new version + the fixed affected packages in one go, to reduce the breakage to a minimum. On Thu, Jul 27, 2017 at 5:55 AM, Martín Ferrari <tin...@tincho.org> wrote: > On 26/07/17 15:46, Shengjing Zhu wrote: > > > I have tested aws-sdk-go 1.4.22 in my local env and also tested it with > > ratt. (I pick 1.4.22 since I hope we don't break too many things.) > > We need to know if this will introduce further regressions, or if it is > API incompatible.. If it is, we would need a new binary package for the > new API > > -- > Martín Ferrari (Tincho) > > _______________________________________________ > Pkg-go-maintainers mailing list > pkg-go-maintain...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers > -- Best regards, Michael
