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

List:       kde-release-team
Subject:    Re: What to do about Kompare?
From:       Sebastian =?iso-8859-1?q?K=FCgler?= <sebas () kde ! org>
Date:       2007-12-11 15:07:09
Message-ID: 200712111607.12664.sebas () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Tuesday 11 December 2007 14:10:36 Matt Rogers wrote:
> On Tuesday 11 December 2007 05:08:09 Tom Albers wrote:
> > Op Tuesday 11 December 2007 03:14 schreef u:
> > > If Kevin wants to take over maintenance, that's fine, but making
> > > Kompare ready for KDE 4.0 seems like a goal not reachable considering
> > > when the release is going to be.

> > Seeing the recent mail about the current state of Kompare from Kevin,
> > which basically tells us it is working and he seems to want to actively
> > maintain the app, do you still have the same opinion? I agree it's pretty
> > late, but if there is an active maintainer and the current stat is ok, I
> > feel we should give Kevin the chance (and motivation) to work on it and
> > include it in four point oh.

> Yes, I still have the same opinion. It's too late. We've already tagged RC2
> and the full release is in less than a month. We need to quit making last
> minute changes like this. What happened to being in "release mode"?
>
> We quit adding new applications to KDE 4.0 months ago. I don't see how
> resurrecting old ones that were previously disabled is any different.

I prefer fixing above removing, if that can be done easily, it should be done. 
As to the freeze, kompare has been shipped for the last releases, so it was 
part of the release (IMO). Having kompare in is a low-risk decision as it 
doesn't touch other components and is a pretty "end-of-the-food-chain" 
application, and since the code to fix it has already been written, no damage 
is done.

Another option would've been to move kompare into extragear, that means that 
it would be released at the same time (most probably) and packagers won't 
find it immediately.

> However, seeing as the change has already been made, it doesn't really
> matter anyways and I have no legs to stand on for an argument anymore. It
> would have been nice if there had been a 24 hour wait period for feedback
> after the initial mail that Allen sent. --

That would be good practise. We ended up doing the same 24 hours grace period 
for decisions in the Marketing Team as well, it adds a bit of safety to those 
taking decisions, which I think is a good thing.
-- 
sebas

 http://www.kde.org | http://vizZzion.org |  GPG Key ID: 9119 0EF9 

["signature.asc" (application/pgp-signature)]

_______________________________________________
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]