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

List:       kde-release-team
Subject:    Re: What to do about Kompare?
From:       Matt Rogers <mattr () kde ! org>
Date:       2007-12-13 13:08:32
Message-ID: FE9CB2E3-63D9-4C3C-A9BD-C8A2EF4B066D () kde ! org
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Dec 13, 2007, at 5:49 AM, Sebastian Kuegler wrote:

> On Thursday 13 December 2007 12:35:29 Mauricio Piacentini wrote:
>>  >I think we might want to bump pretty quickly to a 4.1 release and
>>  >that's when we can enable it again (and move some games and  
>> kaider and
>>  >maybe the ssl tree).
>>
>> Yes, I also think we should not wait more than 3-4 months, and  
>> plan 4.1
>> to the end of April, or May. We all know 4.0 is a release that  
>> will not
>> have everything we need, but at this time we need to have it out :
>>
>> a) with only the components that are working and have been  
>> minimally tested
>> b) soon so that the tree can open again, for new strings, new  
>> ports, new
>> apps
>
> I support this. What I have in mind is roughly the following:
>
> 4th Jan: tagging 4.0, then release
> End of January: 4.0.1 (and possible more bugfix releases as necessary)
> End of January: Opening up trunk/ for features again
> End of March: Feature freeze in trunk
> End of April: 4.1
>
> I'm especially curious how easily we'll be able to stabilise 4.1  
> then. Based
> on that we should decide on some general release schedule strategy,  
> and
> possibly consider a time-based schedule.
>
> How do people feel about this as rough planning?
> -- 

How about starting a new thread for it instead?
- --
Matt


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iD8DBQFHYS7QA6Vv5rghv0cRAlcLAJ9p48XmCZ98AYmoIxj6kCDOi3Ts7ACfde8x
E3dUxlhSMcK07iATQJPZdnk=
=AqVK
-----END 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]