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

List:       kde-commits
Subject:    Re: kdesupport/taglib
From:       Scott Wheeler <wheeler () kde ! org>
Date:       2004-07-19 10:37:08
Message-ID: 200407191237.08975.wheeler () kde ! org
[Download RAW message or body]

On Monday 19 July 2004 12:09, Martijn Pieters wrote:
> Uhoh indeed. That explains the version check I saw you add to Juk then.. 
> I suspect Scott Wheeler is on a holiday; he's not been on IRC for 10 
> days now.

Yes -- I was.  I left on the 9th and just got back last night.
 
> If this code is subject to a feature freeze, how much flexibility is 
> there still in API and functionality changes? Will Scott Wheeler still 
> have room to make changes to your commits with the freeze looming when 
> he comes back?

Well, TagLib doesn't follow the KDE release schedule, so really I have as much 
flexibility as I need.  This did create a mess for me -- especially relative 
to preexisting plans and I'll have to figure out how I'm going to sort things 
out in the next few days.

Here's what I'm thinking at the moment:

*) Branch for 1.2 and revert Allan's changes there.
*) Fix the couple of bugs that I was waiting on finishing before a 1.2 release 
and check this into both branches and release 1.2.  The features that are new 
there have been in CVS for a while and are quite stable; the same can't be 
said for the new features.
*) Mark HEAD as 1.3 and update the configure checks in kde-multimedia.
*) Release a 1.3 beta in the next couple of weeks.
*) If the new stuff seems to be stable enough release 1.3 in time for KDE 3.3.

However I should note that I want to be cautious here since there was some 
serious breakage in KDE 3.2 when Allan checked in FLAC support just before 
the freeze.  The API really shouldn't have been released in the state that it 
was in and it would often corrupt FLAC files that were saved using TagLib.  
As such I must say that I'd like to not rush things now.  People would 
generally rather have their files unsupported than corrupted.  ;-)

-Scott
[prev in list] [next in list] [prev in thread] [next in thread]