On Wednesday 30 April 2014 10:41:30 Raymond Wooninck wrote:
For openSUSE it will definitely bring problems as that we wouldn't be able
to release any maintenance updates anymore for the KDE Desktop with this
Release Cycle. As Sune indicated, if KF5 is updated then the other
components like
On Tuesday 29 April 2014 19:23:07 Scott Kitterman wrote:
For non-rolling distros, at some point you have to stop and release. A mix
of new features and bug fixes aren't going to be allowed in.
We (Kubuntu) have been delivering KDE SC point releases as post-release
updates to our users for
On Wednesday 30 April 2014 05:24:55 Scott Kitterman wrote:
Since we release on a different schedule, with monthly KF5 releases, we'd
all be interested in supporting different releases.
Which is already the case, I mentioned in another reply that Opensuse has had
releases with X.X.5 (so
On Tuesday 29 April 2014 21:54:17 Scott Kitterman wrote:
On April 29, 2014 7:30:50 PM EDT, Albert Astals Cid aa...@kde.org wrote:
El Dimarts, 29 d'abril de 2014, a les 19:23:07, Scott Kitterman va
escriure:
On April 29, 2014 2:07:52 PM EDT, Albert Astals Cid aa...@kde.org
wrote:
El
On Wednesday 30 April 2014 12:04:15 Raymond Wooninck wrote:
On Wednesday 30 April 2014 11:28:26 Àlex Fiestas wrote:
Having a release every month will allow distributions to package fresher
versions of frameworks since we will virtually remove the synchronization
problem.
As an example
On Wednesday 30 April 2014 12:20:51 Luca Beltrame wrote:
Martin Gräßlin wrote:
Hello Martin,
Actually I think there is nothing wrong with having something like an
LTS release which is maintained by the distros. I recently read that
This is going to be difficult, to be honest. I can't
On Wednesday 30 April 2014 08:16:48 Scott Kitterman wrote:
I get what you're asking for.
What I'm trying to make clear is you aren't going to get it.
Well, I'd say we try.
signature.asc
Description: This is a digitally signed message part.
___
On Wednesday 30 April 2014 07:50:02 Scott Kitterman wrote:
The difference is that you will do proper testing with all the QA in
place on
each distros, we don't have such thing upstream beyond the tests.
As for the mess, each distro picks their version as you said and you
(as in
distros)
On Wednesday 30 April 2014 13:44:50 Raymond Wooninck wrote:
So, you will not simply update to 4.14.X but instead do cherry-picking of
the bug fixes? Because that would be the same with Frameworks.
You got that one wrong :) We push the 4.14.x release as a full maintenance
update. So if
On Wednesday 30 April 2014 11:00:39 Lisandro Damián Nicanor Pérez Meyer wrote:
This is a point in which I fully agree, and even if it doesn't solves any of
the things we are discussing it's good to acknowledge: we are very low on
man power, both upstream and most of us dowstreamers.
The amount
On Wednesday 30 April 2014 16:22:43 Ralf Jung wrote:
Hi,
(Disclaimer: I'm not a KDE packager, just a user and an occasional
contributor)
It is, you (as in opensuse) just have to get over the drama of having
small
features in on each release.
Let's try to analyze a bit why some
/116558/diff/
Testing
---
Thanks,
Àlex Fiestas
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
-CREATION
kwalletd/autotests/qtest_kwallet.h PRE-CREATION
kwalletd/autotests/testpamopen.cpp PRE-CREATION
kwalletd/autotests/testpamopennofile.cpp PRE-CREATION
kwalletd/main.cpp f9af414
Diff: https://git.reviewboard.kde.org/r/116555/diff/
Testing
---
Thanks,
Àlex Fiestas
://git.reviewboard.kde.org/r/116558/diff/
Testing
---
Thanks,
Àlex Fiestas
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116555/#review52293
---
On March 2, 2014, 11:33 p.m., Àlex Fiestas wrote
start)
- Àlex
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116555/#review52293
---
On March 2, 2014, 11:33 p.m., Àlex Fiestas
,
and this time it won't have the --login-pam argument, so it won't be affected
by this patch.
So, to summary it:
-It is impossible this breaks anything even if you use the pam module.
- Àlex Fiestas
On March 2, 2014, 11:33 p.m., Àlex Fiestas wrote
the
workflow of the code for urls (dav servers) that are not configured by this
patch.
So, if we imagine that my patch is bugged to the point where it makes the
resource crash, it won't affect other instances of the resource.
- Àlex Fiestas
On March 6, 2014, 7:55 p.m., Àlex Fiestas wrote
/resource/davgroupwareresource.desktop 05264fd
resources/dav/resource/davgroupwareresource.kcfg 2d25371
resources/dav/resource/settings.h e264866
resources/dav/resource/settings.cpp 12f84cc
Diff: https://git.reviewboard.kde.org/r/116558/diff/
Testing
---
Thanks,
Àlex Fiestas
PRE-CREATION
kwalletd/autotests/testpamopennofile.cpp PRE-CREATION
kwalletd/main.cpp f9af414
Diff: https://git.reviewboard.kde.org/r/116555/diff/
Testing
---
Thanks,
Àlex Fiestas
___
release-team mailing list
release-team@kde.org
https
Looks ok, thanks for the work dude!
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111707/#review36559
---
On July 26, 2013, 2:58 a.m., Àlex Fiestas wrote
: This removes a line from the catalog.
Diffs
-
powerdevil/daemon/powerdevilcore.cpp 6874feb
Diff: http://git.reviewboard.kde.org/r/111768/diff/
Testing
---
Notification is not emit anymore.
Thanks,
Àlex Fiestas
___
release-team mailing
/powerdevilhandlebuttoneventsaction.desktop
82f3e1b
Diff: http://git.reviewboard.kde.org/r/111707/diff/
Testing
---
Thanks,
Àlex Fiestas
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
On Thursday 04 July 2013 13:56:20 Sebastian Kügler wrote:
On Thursday, July 04, 2013 01:06:27 Àlex Fiestas wrote:
I want to propose to disable by default KRandR from kde-workspace release
for 4.11.
While I'm considered the maintainer of KRandR truth is I have never been
it, I just made
Hi there
I want to propose to disable by default KRandR from kde-workspace release
for 4.11.
While I'm considered the maintainer of KRandR truth is I have never been
it, I just made it work around 4.7 times but it is still full of bugs and
annoyances.
Since we have KScreen (which tomorrow I will
On Sunday 30 June 2013 20:56:42 Albert Astals Cid wrote:
Is anyone interested at a Release Team BoF for Akademy?
My only avaiable days are thursday-friday.
I would like to have a BoF to discuss a possible switch to 3 month releases,
which will include doing things in a different way.
It is
Sorry for forgetting sending an email to the list. I also give my +1 on the
freeze.
On Tue, May 7, 2013 at 9:34 PM, Albert Astals Cid aa...@kde.org wrote:
El Dimarts, 7 de maig de 2013, a les 09:25:13, Aaron J. Seigo va escriure:
On Tuesday, May 7, 2013 00:51:56 Albert Astals Cid wrote:
Imho this is a good strategy for the 1%, for those applications that need
heavy re-factoring in order to work or make proper use of Qt5 (Plasma and
KWin), however I'm still not convinced that this is a good strategy for the
other 99%.
We could apply the same argument we can use for applications
29 matches
Mail list logo
