Tags Tags

Bug#638741: test results

June 30th, 2012 - 10:10 pm ET by Leo costela Antunes | Report spam
Help Create a new topic
Hi,

Hope you guys don't mind if I just jump in here and try to cool down the
discussion, since it's getting kinda "flamy".

* Goswin von Brederlow wrote:

That was 10 month ago. A revised patch came in December, still 6 month
for you to do something. Your first response was Fri, 29 Jun 2012
23:27:51 +0930.
There is only one person to blame for not applying the patch or raising
concerns about it in a timely fashion and that is you.



Ron mentioned he took over the package a few weeks back [0], so this
blame shifting isn't really accurate (not to mention it's IMHO a bit too
confrontational to be constructive; though I understand you were
reacting to a equally confrontational comment from the previous email).
To get some distance and perspective I'd suggest referring this to the
release-team: if they see the possible downfall as an acceptable
trade-off for the multi-arch release goal, then go ahead with the
patching, uploading and fixing bugs as they appear. Otherwise leave it be.


Cheers

[0] http://packages.qa.debian.org/liba/...1911Z.html

Leo "costela" Antunes
[insert a witty retort here]




To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
email Follow the discussionReplies 1 replyReplies Make a reply

Replies

#1 Ron
July 01st, 2012 - 12:50 am ET | Report spam
On Sun, Jul 01, 2012 at 03:58:45AM +0200, Leo 'costela' Antunes wrote:
Hi,

Hope you guys don't mind if I just jump in here and try to cool down the
discussion, since it's getting kinda "flamy".



Yeah, that tends to happen when people get tired of repeating themselves
to Goswin, and he keeping wanting to harp on about it ...

This already got resolved on IRC, and I only replied here to make it clear to
anyone looking at the bug that this really was off the table for Wheezy now.
The discussion can't really get much cooler than "Wheezy is now frozen".

To get some distance and perspective I'd suggest referring this to the
release-team: if they see the possible downfall as an acceptable
trade-off for the multi-arch release goal, then go ahead with the
patching, uploading and fixing bugs as they appear. Otherwise leave it be.



So let's not annoy them with this now please. The only possible outcome of
doing this now for them is "more pain and more work and more delays before
we are in a state to release".

It will make it impossible for them to binNMU this package should it need it,
and it will burn up their time needing to review patches that really aren't
fixing anything that is remotely release critical. And they already have
enough people requesting crazy freeze exceptions from them ...

If nobody noticed they needed an m-a version of this before now, then clearly
it's not a high priority for them, and it can easily wait until there is a
better time to start experimenting with this again.

The sooner the remaining RC bugs are fixed and we release, the sooner that
will happen. This is how release cycles work. It's too late for untested
things now.


But thanks for the good intentions,
Ron





To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact

Similar topics

Make your own search :