kdepim4.5

[Eli Wapniarski]

On Friday 02 July 2010 20:25:33 Thomas Janssen wrote:
> On Fri, Jul 2, 2010 at 7:04 PM, Eli Wapniarski <eli at orbsky.homelinux.org> 
wrote:
> > On Friday 02 July 2010 18:03:10 Rex Dieter wrote:
> >> Christoph Kaulich wrote:
> >> > just a short question, will there be a kdepim 4.5 beta1 build for
> >> > fc13?
> >> 
> >> When it is provided by it's upstream.
> >> 
> >> Turns out just yesterday, some preliminary kdepim-4.5-beta1 tarballs
> >> were provided to packagers, so we'll get to work on those, and get into
> >> rawhide and kde-unstable asap.
> > 
> > Errr.... What does that say about stability?  If I recall correctly there
> > were serious issues with kdepim 4.5 that delayed the release with kde
> > 4.5. Does that mean the developers think that they have been resolved?
> > If not is it wise to include kdepim 4.5 so deep in the release cycle?
> 
> Kdepim 4.5 will be released (the final version) together with KDE SC
> 4.5.1 or 4.5.2 (of course if the developers think it's ready then,
> what it look like from a todays POV). Means yes, it is wise to include
> it in the release cycle of rawhide.


OK then here are my real questions... Will kdepim 4.4 accompany kde 4.5 in 
unstable? If kdepim 4.5 turns out to be unusable (not beyond the realm of 
possibilities given kdepim's 4.x's history and what is already known about 
kdepim 4.5) then how to downgrade back to 4.4 and not screw up kdepim  and 
akonadi due to all the configuration changes that no doubt will accompany the 
upgrade to 4.5? As asked previously... Is it wise to include kdepim 4.5 so 
late in the release cycle when we already know that it isn't going to be 
included in the final release of kde 4.5? And since I really do not want to run 
kdepim 4.5 on my computer because I know it doesn't work anywhere close to 
where it should will I be able to maintain the current kdepim 4.4 with kde 4.5 
as things stand at the moment?

Rawhide fine.... kde-unstable???? hmmmmm... I dunnoooo.

Eli

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.