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

List:       koffice-devel
Subject:    Re: libkdchart api stability?
From:       Johannes Simon <johannes.simon () gmail ! com>
Date:       2010-03-23 11:50:25
Message-ID: F6E557EE-F1F8-4DD3-B233-88E9D5E48E62 () gmail ! com
[Download RAW message or body]

Though I agree with Thomas, I would argue in a different way. What Carlos says can really be applied to \
all software projects out there. No library that a project depends on is ever 100% bug free, but software \
developers have to live with that, otherwise larger modular systems (take any linux distro for instance) \
would be a huge mess, each and every software package shipping their own bug-fixed version of the same \
library. It is not any different for KOffice.

There's exceptions to the rule, e.g. when a library is too unstable, or in a beta stage, then you use \
your local copy and apply all bug fixes you need to make it work for you. But this is not the case with \
KDChart. It's been in a stable state for a long time. If you do find a bug, there's very likely a \
work-around for it that you can use until the bug-fixed version has been released.

Bottom line is, KDChart is not different from other libraries that KOffice depends on.

- Johannes

Am 23.03.2010 um 08:55 schrieb Thomas Zander:

> On Tuesday 23. March 2010 05.39.01 Carlos Licea wrote:
> > I would vote for keeping the copy in KOffice for the time being. Otherwise
> > we  could jeopardize responsiveness in bug fixing.
> 
> I'm sorry to say, but for that reason I think the exact opposite should 
> happen.
> From experience it shows that if its easy to get your fix in your local tree 
> then the incentive to do the right thing and push it upstream becomes an 
> afterthought that in my experience is dropped too often.
> 
> If Nokia needs a fix that didn't make it into a release yet then there are 
> several options available for it to include the patch in the actual build it 
> ships. All of them suboptimal, but thats the point; it should go upstream.
> 
> Please, if possible setup the open source environment in such a way that the 
> right thing to do is the easiest solution. That way you avoid a lot of 
> management and end up with a more sustainable long term ecology.
> -- 
> Thomas Zander
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@kde.org
> https://mail.kde.org/mailman/listinfo/koffice-devel

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel


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