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

List:       kde-release-team
Subject:    Re: [Kde-pim] Re: kdepimlibs and kdateedit
From:       John Layt <johnlayt () googlemail ! com>
Date:       2010-11-30 11:37:12
Message-ID: 201011301137.13192.johnlayt () googlemail ! com
[Download RAW message or body]

On Tuesday 30 November 2010 10:18:39 Kevin Ottens wrote:
> Sorry if the wording turned out unfortunate it wasn't my intent there. It
> was more about a reality check:
>  a) I can't devote much time to it on a regular basis (it's rather low on
> my priority list), and I think I'm not the only one with that problem
> since I hear this "let's move KDateEdit to kdelibs since *at least* 4.3";
>  b) Until it's in kdelibs people will keep doing stuff in their own corner,
> so the work I did so far will need to be done again for missing features
> and so on, David's mail actually illustrate that well... The feature he
> refers to wasn't there when I started. :-/
> 
> But OK, looks like I missed the window by a couple of weeks, so let's make
> it for a "later release".
> 
> Regards.

OK, so if it can't be in 4.6, how's this for a plan:
* Merge Kevin's changes into the kdepim version so they are not lost and 
kdepim gets the benefit in the interim.
* I bug fix the merged version in kdepim to fix the localization problems
* Advertise loudly to all the projects with forks of KDateEdit that they may 
want to update their copy from kdepim.
* When trunk reopens, we move to kdelibs and I'll start hacking on it

Cheers!

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