On Wednesday 16 November 2011 21:32:35 Patrick Spendrin wrote:
> Well, theoretically the kde-4.7 branch should contain the stable builds
> - which means that external packages should have their default target on
> a stable release (e.g. soprano, poppler, win32libs-sources, etc.) and
> the KDE packages on the release branch (which is KDE/4.7 for kde-4.7).
> Also, for the KDE packages, all the stable releases should be in the
> kde-4.7 branch (for kmymoney e.g. the 4.6.1 release) which is where the
> differences come from - the master branch doesn't contain the releases.

I can partly understand this approach but partly not. If it look at it this
way: all software from trunk/master is in development and thus unstable then I
agree but that not true in all cases. From an application developer's POV the
main goal is to get it's software to the user as fast as possible (after a
release or even from trunk). If you think about it this way then the
stable/unstable principle is only applicable to the platform itself that being
KDE (win32libs, qt, kdelibs, kdepimlibs, kderuntime).

A problem in one application is not as serious as a problem in the platform
itself (kio crashes vs. some app. crash in a certain scenario).

As an application developer I would need a stable KDE platform on Windows.
AFAIK KDE applications don't really need the latest KDE to be build-able (even
from trunk/master). So I would strongly agree to developing kmymoney on
Windows on top of KDE 4.7.3 instead of developing it on top of KDE master
which can't be done since building kdelibs master fails.

So once a relatively stable KDE release is obtained I would make it somehow
available as a development platform for application developers thus letting
the KDE on Windows project members focus on issues with the KDE platform
itself.

--
Regards,

Cristian Oneț

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Kde-windows mailing list
Kde-windows@kde.org
https://mail.kde.org/mailman/listinfo/kde-windows

Reply via email to