On Sunday, June 10, 2012 01:22:03 Kevin Kofler wrote:
On Sunday 10 June 2012, Nicolás Alvarez wrote:
Why not start now and make the next kdelibs 4.8.5? Releasing a kdelibs
4.9 will just add to the confusion of how kdelibs development is
working.
Because having a kdelibs version different
On Monday, June 11, 2012 07:20:50 AM Sebastian Kügler wrote:
On Sunday, June 10, 2012 01:22:03 Kevin Kofler wrote:
On Sunday 10 June 2012, Nicolás Alvarez wrote:
Why not start now and make the next kdelibs 4.8.5? Releasing a kdelibs
4.9 will just add to the confusion of how kdelibs
On 2012-06-11, Sebastian Kügler se...@kde.org wrote:
I'd consider that a bug in your packaging. There's no absolute requirement of
an app for a specific version of kdelibs. If your packages need that, you
should probably fix them. The decoupling of libs and apps, and especially the
On Monday, June 11, 2012 16:25:17 Scott Kitterman wrote:
Currently my About KDE says:
Platform Version 4.8.3 (4.8.3)
Once kdelibs versioning is desynchronized from the rest of the platform,
what version is it?
At least application-version and underlying-platform-version might (or might
Kevin,
On Saturday, June 09, 2012 23:20:16 Kevin Kofler wrote:
you are hurting everyone else trying to package Plasma Active.
You should start considering that we're actually creating the thing. If we had
promised you it was fit for general consumption by any distro packager, you
might have
Hello,
here at Debian we had a really bad experience with 4.8.4. While 4.8.3 was
pretty good, 4.8.4 seemed like a huge step backwards in terms of stability
(random crashes there and there). After quick investigation of kdelibs 4.8.4
I found the following:
$ diff -uNr kdelibs-4.8.3 kdelibs-4.8.4
On Saturday 09 June 2012, Modestas Vainius wrote:
I don't know yet if any other modules from 4.8.4 has been
mis-packaged in the same way
Due to the permanent feature freeze of kdelibs 4, there is actually no
difference between kdelibs 4.8.4 and 4.8.80/4.8.90 other than the version
number,
El Dissabte, 9 de juny de 2012, a les 10:35:15, Modestas Vainius va escriure:
Hello,
Hi
here at Debian we had a really bad experience with 4.8.4. While 4.8.3 was
pretty good, 4.8.4 seemed like a huge step backwards in terms of stability
(random crashes there and there). After quick
Hello,
On šeštadienis 09 Birželis 2012 13:01:20 Albert Astals Cid wrote:
here at Debian we had a really bad experience with 4.8.4. While 4.8.3 was
pretty good, 4.8.4 seemed like a huge step backwards in terms of
stability (random crashes there and there). After quick investigation of
On 06/09/2012 12:10 PM, Modestas Vainius wrote:
Hello,
On šeštadienis 09 Birželis 2012 13:01:20 Albert Astals Cid wrote:
here at Debian we had a really bad experience with 4.8.4. While 4.8.3 was
pretty good, 4.8.4 seemed like a huge step backwards in terms of
stability (random crashes there
El Dissabte, 9 de juny de 2012, a les 13:10:40, Modestas Vainius va escriure:
Hello,
On šeštadienis 09 Birželis 2012 13:01:20 Albert Astals Cid wrote:
here at Debian we had a really bad experience with 4.8.4. While 4.8.3
was
pretty good, 4.8.4 seemed like a huge step backwards in
El Dissabte, 9 de juny de 2012, a les 12:28:11, Andreas K. Huettel va
escriure:
Am Samstag 09 Juni 2012, 12:10:40 schrieb Modestas Vainius:
Hello,
On šeštadienis 09 Birželis 2012 13:01:20 Albert Astals Cid wrote:
here at Debian we had a really bad experience with 4.8.4. While 4.8.3
On Saturday 09 June 2012, Albert Astals Cid wrote:
There is not stupid not weird thing in kdelibs. We simply declared kdelibs
to be feature perfect and only bugfixes should be happening there.
What's the problem with that?
That no software is ever perfect.
For example, we will NEED the
On Saturday, June 09, 2012 11:58:44 Kevin Kofler wrote:
Yes, it's stupid, but it's how the kdelibs maintainers want things to be.
:-(
There's a difference between I don't follow the reasoning or I don't think
the maintainer's reasons are valid and stupid.
Please be more respectful, or go
On Saturday, June 9, 2012 12:20:23 Andreas K. Huettel wrote:
rewritten or broken. However, imposing this branch weirdness on everyone
else for pure political reasons is just wrong.
it isn't for political reasons.
kdelibs development is focusing on 5.0. there are no further feature releases
On Saturday, June 9, 2012 13:10:40 Modestas Vainius wrote:
There's no mispackaging. If you followed the list or read the archives
before blaming people of wrong doing you'd know that kdelibs for 4.8.4 and
4.8.80 actually come from the same branch.
Thank you for pushing a bunch of untested
On Saturday, June 9, 2012 13:40:29 Andreas K. Huettel wrote:
Am Samstag 09 Juni 2012, 12:57:16 schrieb Aaron J. Seigo:
now, i really don't understand the use of words like stupid and dumb.
I'll leave the fist fighting to others, and would like to apologize for my
choice of words.
cool;
Am Samstag 09 Juni 2012, 11:58:44 schrieb Kevin Kofler:
On Saturday 09 June 2012, Modestas Vainius wrote:
I don't know yet if any other modules from 4.8.4 has been
mis-packaged in the same way
Due to the permanent feature freeze of kdelibs 4, there is actually no
difference between
Am Samstag 09 Juni 2012, 12:37:28 schrieb Albert Astals Cid:
You are all making noise out of nothing, the amount of changes is in the
same order of magnitude of other releases.
Please stop let's stop throwing shit to the other side of the fence and
start being constructive
Actually you're
Am Samstag 09 Juni 2012, 12:57:16 schrieb Aaron J. Seigo:
now, i really don't understand the use of words like stupid and dumb.
I'll leave the fist fighting to others, and would like to apologize for my
choice of words.
I still dont think the decision to freeze master was a good or necessary
Hi,
I've run the compatibility test against the 4.8.3 and 4.8.4 versions of
KDE-libs using the ABI Compliance Checker tool and got the following
report:
http://upstream-tracker.org/compat_reports/kde-libs/4.8.3_to_4.8.4/compat_report.html
The report shows that the API/ABI structure is not
On Saturday, June 9, 2012 17:23:44 Andrey Ponomarenko wrote:
I've run the compatibility test against the 4.8.3 and 4.8.4 versions of
KDE-libs using the ABI Compliance Checker tool and got the following
report:
this is remarkably useful. thanks! are we running this on every release? if
not,
On Saturday, 2012-06-09, Aaron J. Seigo wrote:
On Saturday, June 9, 2012 17:23:44 Andrey Ponomarenko wrote:
I've run the compatibility test against the 4.8.3 and 4.8.4 versions of
KDE-libs using the ABI Compliance Checker tool and got the following
report:
this is remarkably useful.
On 09/06/12 14:30, Aaron J. Seigo wrote:
personally, i think it is completely unnecessary and that we should all get
used to it now because it could happen in future that Frameworks are released
on a different release cycle to applications so that kdelibs version ==
workspaces version will
On 09/06/12 21:53, Alex Merry wrote:
On 09/06/12 14:30, Aaron J. Seigo wrote:
personally, i think it is completely unnecessary and that we should all get
used to it now because it could happen in future that Frameworks are
released
on a different release cycle to applications so that
On Saturday 09 June 2012, Aaron J. Seigo wrote:
things that change APIs, that do not leave kdelibs non-useful on large %s
of user systems, etc. would therefore not meet the likely requirements.
and i say that as someone who is sitting on patches to kparts (written by
Ivan, not me :) that i
Thank you for pushing a bunch of untested huge changes in the minor
point
release. Really appreciated.
what are those untested changes please?
+1.
Bit of nitpick about wording, but 4.8.4 is a new patch level release, not minor.
Best Regards,
Laszlo Papp
El 09/06/2012, a las 10:30, Aaron J. Seigo ase...@kde.org escribió:
On Saturday, June 9, 2012 13:40:29 Andreas K. Huettel wrote:
Am Samstag 09 Juni 2012, 12:57:16 schrieb Aaron J. Seigo:
now, i really don't understand the use of words like stupid and
dumb.
I'll leave the fist fighting to
On Sunday 10 June 2012, Nicolás Alvarez wrote:
Why not start now and make the next kdelibs 4.8.5? Releasing a kdelibs
4.9 will just add to the confusion of how kdelibs development is
working.
Because having a kdelibs version different from (and especially lower than) the
KDE SC version messes
29 matches
Mail list logo
