On Tuesday 05 June 2012, Albert Astals Cid wrote:
> On May 19, Dawit Alemayehu commited a change that uses
> QSslConfiguration::testSslOption that is only available in Qt 4.8
>
> This means that both kdelibs 4.8.4 and kdelibs 4.9 now depend in Qt 4.8
> instead Qt 4.7
Hi Albert,
thanks for noti
On Tuesday 20 December 2011, Davide Bettio wrote:
> On Tuesday 20 December 2011, Dirk Mueller wrote:
> >Perfectly fine with that if you can do it now and not break anything and
> >make it all work smoothly. As I think that is a too short notice, lets do
> >it for 5.0.
>
&
Hi,
As a preparation of KDE 4.8 RC1 I've created a KDE/4.8 branch for all released
modules except for kdelibs, where I'm waiting for feedback if creating a 4.8
branch makes sense for just one patch (see other mail today).
Please remember that from now on, any change that should be part of KD
On Tuesday 20 December 2011, Davide Bettio wrote:
> I'm sorry to discuss this thing now, but I've seen all the new artworks
> recently. Anyway the point is that everything will remain in kde-workspace
> history forever so moving it away at that point will not decrease space
> usage
I know, but it
On Tuesday 20 December 2011, Davide Bettio wrote:
> As every year some artworks are changed according to the new default
> desktop background. This year I noticed some problems:
>
> 1) kdm and ksplash default theme is part of kde-workspace. I need to update
> both, but if I do that I will have to
On Thursday 29 September 2011, Kevin Kofler wrote:
> 2. It will be confusing to our users, and even to some packagers, to have a
> KDE SC 4.8 on kdelibs 4.7. The rule so far has always been that the kdelibs
> version must be the same as the KDE SC version. Changing this will also
> break all our F
On Saturday 21 May 2011, Tom Albers wrote:
> According to http://bugs.kde.org/273783 KIO is broken. Although this could
> be introduced after Dirks tag, but that would mean someone broke the tag
> freeze.
>
> Can someone confirm and find a solution ASAP?
Hi Tom,
Thank you for letting me know.
Hi,
in the past we used to have the rule that kdelibs provides a stable ABI
backward compatible API. When the need for experimental, not yet mature
libraries came up, we introduced kdelibs/experimental.
Back then, the rule was that no stable public API must depend on experimental,
ABI-unsaf
On Thursday 19 May 2011, Stephen Kelly wrote:
> The beta tagging is due to happen today. As far as I know this hasn't been
> addressed. Was it more complex than expected or you just didn't have time?
>
> I propose that we revert the dependency bump and tell packagers they need
> to package a vers
Hi guys,
could somebody please summarize for me which git modules should be part of KDE
4.7 beta1 and which ones shouldn't?
Thanks,
Dirk
On Wednesday 19 January 2011, Dirk Mueller wrote:
> so the general consensus seems to be against slipping the schedule and
> inserting a RC3.
>
> This means that we need to solve bug 246678. Given that there seems to be
> no fix in sight (no comment in the last 14 days), can we
SVN commit 1208598 by mueller:
Creating a KDE 4.6 branch
CCMAIL: release-t...@kde.org
CCMAIL: kde-core-devel@kde.org
A 4.6 (directory)
12 matches
Mail list logo
