On 27/07/17 14:05, Michael Stapelberg wrote:
> 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?

We had to do it once, for golang-github-dgrijalva-jwt-go-v3-dev

Worth the trouble or not: depends on who gets to fix all the breakage
left behind :)

> Personally, I would just update the new version + the fixed affected
> packages in one go, to reduce the breakage to a minimum.

I would be OK with that.

-- 
Martín Ferrari (Tincho)

_______________________________________________
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

Reply via email to