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

List:       kde-release-team
Subject:    Re: Initial revision of KDE 4.1 schedule available on Techbase
From:       Dirk Mueller <mueller () kde ! org>
Date:       2008-02-13 1:01:10
Message-ID: 200802130201.10537.mueller () kde ! org
[Download RAW message or body]

On Saturday 26 January 2008, Matt Rogers wrote:

> I've posted a new schedule on
> http://techbase.kde.org/index.php?title=Schedules/KDE4/4.1_Release_Schedule
> that should work as the nearly final release schedule.
>
> Feedback is appreciated.

I have a couple of questions: 

a) "Binary compatibility is not required". what do you mean by that? you're 
saying that newly added features do not have to be binary compatible? you're 
saying that binary incompatible changes are allowed in kdelibs?

b) Why a hard feature freeze for alpha1, e.g. before any user announced 
release? that doesn't make sense. we should have alpha releases that attract 
user attention and be able to react to the feedback, which often means 
changing or implementing new features. imho the feature freeze shouldn't be 
before beta1 or beta2. 

c) Why a message freeze before beta1? bugfixes often require message changes. 

d) it is still a mis-aligned schedule, however I'm not going to complai too 
loudly about it given that it might slip by one month and then be aligned :)

e) I like the no-new-artwork freeze. 

Greetings,
Dirk
_______________________________________________
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]