[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-release-team
Subject:    Re: showstoppers
From:       Sebastian =?utf-8?q?K=C3=BCgler?= <sebas () kde ! org>
Date:       2010-02-09 11:22:37
Message-ID: 201002091222.40152.sebas () kde ! org
[Download RAW message or body]

On Tuesday 09 February 2010 11:33:03 John Tapsell wrote:
> On 9 February 2010 10:17, Dirk Mueller <mueller@kde.org> wrote:
> > On Tuesday 09 February 2010, John Tapsell wrote:
> >> >> What about the transmitting-reserved-utf8-characters crash?  I
> >> >> thought we agreed that that was a showstopper as well?
> >> >> https://bugs.kde.org/show_bug.cgi?id=199485
> >> > 
> >> > We didn't. It's not a regression over 4.3, so no use in holding the
> >> > release back for that one. It needs fixing nevertheless, of course.
> >> 
> >> I object to this way of thinking.  Such an easy remote-exploit should
> >> not be allowed - especially one that seems straight forward to fix.

> > the bugreport you mention is about a krunner crash that has no patch
> > attached. are we talking about the same thing?
> 
> Yes - note that the bug has the keywords "kde-4.4.0-blocker", signed
> off by Thiago. Although the more "useful" bug report is actually
> http://bugs.kde.org/show_bug.cgi?id=219985 which has been fixed on
> konversation side, but not on the knotify side.

Note that I fully agree that it needs fixing ASAP, but it just makes no sense to 
hold up 4.4.0 for it, as it's not a regression. Not releasing 4.4.0 now does not 
have any influence on fixing this bug.
-- 
sebas

http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
[prev in list] [next in list] [prev in thread] [next in thread]