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

List:       kde-release-team
Subject:    Re: Tagging & Release delayed for KDE SC 4.4-beta1
From:       Eike Hein <hein () kde ! org>
Date:       2009-11-29 21:14:39
Message-ID: 4B12E43F.60309 () kde ! org
[Download RAW message or body]

On 11/29/2009 09:48 PM, Allen Winter wrote:
> I might agree, except that I literally have not been able to
> run KOrganizer trunk at all for the past couple of *weeks*.
> 
> I have no idea what the quality of KOrganizer trunk is.
> 
> I will have no way of fixing any bugs at all in KOrganizer 4.4
> until this is dealt with.  Basically, we'd be throwing KOrganizer
> out there and just hoping for the best.  I can't do that as maintainer
> of this application, nor as the kdepim module coordinator.

Right ... hmhm.

It's true of course that pushing the beta out breaks the
feedback cycle for KOrganizer needed for a good final re-
lease if the final's release date were to stay the same.

But delaying the beta likely also means delaying the re-
lease date. If we delay the release date, we might as well
just release beta 1 as scheduled and rather add a third
beta to the schedule. Then the other apps would have a
longer beta feedback cycle rather than waiting on KOrga-
nizer to release beta 1, and KOrganizer, assuming it
works again by beta 2 of 3, would have one like it would
have had if it had worked in beta 1.

Basically, keeping everything on the established beta
schedule and simply extending the beta cycle seems like
a better opportunity for 4.4's quality than delaying the
whole beta cycle over KOrganizer, no?

Perhaps KOrganizer could be disabled from build for beta
1, and then switched back on for beta 2 (out of a propo-
sed 3)?


-- 
Best regards,
Eike Hein
_______________________________________________
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]