On Sun, Aug 19, 2012 at 11:07 PM, Mike Frysinger <vap...@gentoo.org> wrote: > On Sunday 19 August 2012 04:41:17 Luca Barbato wrote: >> On 8/18/12 5:31 AM, Mike Frysinger wrote: >> > i'll probably land it later this weekend/monday. >> >> Would be nice having a list of bugs open so people might have a look and >> see if there is something big left. > > we've been making trackers for the glibc upgrades: > https://bugs.gentoo.org/show_bug.cgi?id=glibc-2.16
While trackers are of course the right way to handle this, it is generally best to announce timelines more than two days in advance. You're certainly not the only case of this problem - I've noticed a tendency to post a tracker for some issue, watch nothing happen for six months, and then see an announcement that the change is being pushed through in a few days. Changes with a big impact should be announced on the lists well before they are made. Also, while users running unstable systems are naturally going to be at risk for unforeseen issues, this isn't an unforeseen issue. When we know a problem exists, we generally should fix it before we commit it. If some uncommon package breaks I think we can live with that, but gnutls doesn't fall into that category. I'm not really interested in the blame game either. This isn't your problem, or the gnutls maintainer's problem - this is Gentoo's problem, and I hope we don't make it our user's problem for failure to work together. Rich
