Hey all,

As you all know, the freeze is getting close, and we are all working to
get our packages in shape for Stretch.

We have a few big projects that share many common dependencies. This
being the golang ecosystem, we are walking in a minefield.

Only two days ago we had a big breakage introduced by API breaking
changes in libraries, without upstream using any kind of SONAME change.
I think it is the first time I see this happening, but it will only get
worse as we package more parts of the golang world.

Personally, I have been working for 1.5 years in getting Prometheus
ready for Stretch. I know many people here have devoted comparable
amounts of time in other projects. So let's all be considerate of these
efforts and be very careful not to break things.

It was removed from testing yesterday, and I hope to have it back in a
few days, but if it breaks again because of a change in another package,
I think I am going to go postal :-)

So that, let's all be excellent to each other!

PS: I am thinking that we should have some kind of automated ratt setup
(maybe even a private upload queue that runs ratt and then automatically
uploads to sid, and make that mandatory policy for the team), but I
don't really have the bandwidth now to implement it. Anybody else thinks
that would be a good idea?

Martín Ferrari (Tincho)

Pkg-go-maintainers mailing list

Reply via email to