Git commit 866a38766e5c33ef81e9f2434f6d8995bd5f1aea by Ben Cooksley.
Committed on 08/06/2017 at 06:29.
Pushed by bcooksley into branch 'master'.

Move Zanshin to KDE Review.
CCMAIL: <a href="mailto:kde-core- ... at kde dot org">kde-core- ... at kde dot org</a>
Fixes T6277

R +0 -0 projects/kdereview/zanshin/i18n.json [from: projects/playground/pim/zanshin/i18n.json - 100% similarity]
R +1 -1 projects/kdereview/zanshin/metadata.yaml [from: projects/playground/pim/zanshin/metadata.yaml - 089% similarity]

<a href="https://commits.kde.org/sysadmin/repo-metadata/866a38766e5c33ef81e9f2434f6d8995bd5f1aea" title="https://commits.kde.org/sysadmin/repo-metadata/866a38766e5c33ef81e9f2434f6d8995bd5f1aea">https://commits.kde.org/sysadmin/repo-metadata/866a38766e5c33ef81e9f2434...</a>

diff --git a/projects/playground/pim/zanshin

Hi all,
The Kirigami component set always was targeted to be eventually released as a
framework, ideally tier 1.

Good morning everyone,
For you that don't know me, I'm Lays Rodrigues, and I work with 3 more
guys(Patrick, Chris, Tomaz) on Atelier.
Atelier is a software for 3DPrinting that we are building inside KDE.

Hi all,
I'm anouncing the QtQuickControls2 desktop style in kdereview, repo name is
qqc2-desktop-style

It is intended to be a small style written in QML for QtQuickControls2 that is
intended to be used by default in QQC2-based apps when used in the Plasma
desktop (it shouldn't have any user-visible message, anywhere), its final
intended location is kde/workspace to be released together with Plasma 5.11

13th May 2017. KDE today announces the release of KDE Frameworks 5.34.0.

KDE Frameworks are 70 addon libraries to Qt which provide a wide variety of·
commonly needed functionality in mature, peer reviewed and well tested·
libraries with friendly licensing terms.

GENERAL INFO

BUILD UNSTABLE
Build URL: <a href="https://build.kde.org/job/kdelibs%20KDE-4.14%20latest-qt4/PLATFORM=Linux,compiler=gcc/79/" title="https://build.kde.org/job/kdelibs%20KDE-4.14%20latest-qt4/PLATFORM=Linux,compiler=gcc/79/">https://build.kde.org/job/kdelibs%20KDE-4.14%20latest-qt4/PLATFORM=Linux...</a>
Project: PLATFORM=Linux,compiler=gcc
Date of build: Fri, 12 May 2017 00:39:57 +0000
Build duration: 48 min

CHANGE SET
Revision 2c2892f07cc052a9f3d52b73b4b03d4637142a31 by scripty: (SVN_SILENT made messages (.desktop file))
change: edit knotify/tests/knotifytest.notifyrc
change: edit kio/misc/kmailservice.desktop
change: edit kdecore/network/kssld/kssld.desktop
change: edit kparts/tests/notepad.desktop
change: edit plasma/tests/testcontainmentactionsplugin

GENERAL INFO

BUILD UNSTABLE
Build URL: <a href="https://build.kde.org/job/kdelibs%20KDE-4.14%20latest-qt4/PLATFORM=Linux,compiler=gcc/77/" title="https://build.kde.org/job/kdelibs%20KDE-4.14%20latest-qt4/PLATFORM=Linux,compiler=gcc/77/">https://build.kde.org/job/kdelibs%20KDE-4.14%20latest-qt4/PLATFORM=Linux...</a>
Project: PLATFORM=Linux,compiler=gcc
Date of build: Mon, 08 May 2017 10:54:07 +0000
Build duration: 33 min

CHANGE SET
Revision 92273b7d8cf039b80c310971a4216c8736dae48f by Albert Astals Cid: (Prepare for 4.14.32)
change: edit README
change: edit cmake/modules/KDE4Defaults.cmake
change: edit CMakeLists.txt

JUNIT RESULTS

Name: (root) Failed: 2 test(s), Passed: 161 test(s), Skipped: 0 test(s), Total: 163 test(s)Failed: TestSuite.kdecore-ksycocathreadtestFaile

Hi everyone,

This is going to be quite a long email, my apologies in advance for that.
If you use the CI system regularly as part of your development flow it
is important you read this email in it's entirety as your action will
probably be required. If you are aware of a list I have missed in the
above, please feel free to forward it there.

As some will have been aware of for some time we currently have a
problem where changing the system base is an incredibly disruptive
activity.

Hi all,

I hit a bug[1][2] in kde-open5 when using
QDesktopServices::openUrl(myUrl) to open the system browser.

The issue is that, since myUrl redirects to another page, kde-open5
(used under the hood by QDesktopServices because
XDG_CURRENT_DESKTOP=KDE is set) "fetches" the redirection url and then
open the browser at the redirected url; for my workflow this is bad
because myUrl generate a cookie and then you have no such cookie when
the browser starts.

I debugged the flow and I understood that since
redirectionHandlingEnabled is enabled by default, this[3] statement in
transferjob.cpp handl

Git commit 01bc4814fa11272f54e6f33f7a3f3e2ae883913c by Ben Cooksley.
Committed on 27/04/2017 at 09:59.
Pushed by bcooksley into branch 'master'.

Move kdepim-runtime to kde/pim/ in the virtual hierarchy.
WARNING: All projects which depend on kdepim-runtime on the CI system will be broken until kdepim-runtime has been rebuilt following this commit.

Hi,

we have talked about the above topics a couple of times in the past, from what
I remember usually agreeing it would be nice to have some more statistical
information about our users, so we know what our applications are used for,
and to measure impact of changes. Similarly, it would be nice to be able to
actually ask our users questions without statistical bias by using out-of-band
channels like blogs or social media.

Hi,

just wondering if I'm doing something wrong or there really is a bug in KDirWatch
(I'm on openSuse Leap 42.2, KF5 5.33.0)

From the docs I understand that when I call

KDirWatch::stopDirScan(dir);
... create files in the dir ...
KDirWatch::restartDirScan(dir)

it should not emit the dirty signal when I run this, right ?

Well, it does.
I've attached a small test.

When I modify the code and use stopScan() ... create ... startScan()
I still receive the dirty signal with the path to the file I created.

Only way it works without signal is
removeDir(dir) ... create ...

Hey all,

how is one supposed to install different versions of icons for different icon
themes? Say I have an icon for breeze, breeze-dark and oxygen. I went ahead
and plumbed it into CMake with ECM's ecm_install_icons specifying THEME
accordingly, but at runtime nothing is found...

08th April 2017. KDE today announces the release of KDE Frameworks 5.33.0.

KDE Frameworks are 70 addon libraries to Qt which provide a wide variety of·
commonly needed functionality in mature, peer reviewed and well tested·
libraries with friendly licensing terms.

I'm trying to make Krita use QSaveFile instead of the home-grown
mess of temporary files that get copied over the original file
after saving succeeded. The problem is that Krita, like Calligra,
uses KArchive.

GENERAL INFO

BUILD UNSTABLE
Build URL: <a href="https://build.kde.org/job/kdelibs%20KDE-4.14%20stable-qt4/PLATFORM=Linux,compiler=gcc/75/" title="https://build.kde.org/job/kdelibs%20KDE-4.14%20stable-qt4/PLATFORM=Linux,compiler=gcc/75/">https://build.kde.org/job/kdelibs%20KDE-4.14%20stable-qt4/PLATFORM=Linux...</a>
Project: PLATFORM=Linux,compiler=gcc
Date of build: Mon, 27 Mar 2017 12:20:43 +0000
Build duration: 23 min

CHANGE SET
Revision ff6a9a25c6fb7358460d4ae2164313a4e58a514b by rakuco: (khtml: Delete pointer _before_ returning.)
change: edit khtml/ecma/kjs_html.cpp

JUNIT RESULTS

Name: (root) Failed: 5 test(s), Passed: 158 test(s), Skipped: 0 test(s), Total: 163 test(s)Failed: TestSuite.kfile-kdiroperatortestFailed: TestSuite.kio-clipboardupdatertestFailed: TestSuit

11th March 2017. KDE today announces the release of KDE Frameworks 5.32.0.
(this time for real -- last time it was in fact 5.31 with a bug in the version in the announcement email...)

KDE Frameworks are 70 addon libraries to Qt which provide a wide variety of·
commonly needed functionality in mature, peer reviewed and well tested·
libraries with friendly licensing terms.

Git commit b8559f750bfa648ebae4a26882b2a64f07ae3094 by Ben Cooksley.
Committed on 07/03/2017 at 06:24.
Pushed by bcooksley into branch 'master'.

Move Plasma Vault to (Plasma) Workspace
Fixes T5335
CCMAIL: <a href="mailto:release- ... at kde dot org">release- ... at kde dot org</a>
CCMAIL: <a href="mailto:kde-core- ... at kde dot org">kde-core- ... at kde dot org</a>
CCMAIL: <a href="mailto:plasma- ... at kde dot org">plasma- ... at kde dot org</a>

R +0 -0 projects/kde/workspace/plasma-vault/i18n.json [from: projects/kdereview/plasma-vault/i18n.json - 100% similarity]
R +1 -1 projects/kde/workspace/plasma-vault/metadata.yaml [from: projects/kdereview/plasma-vault/metadata.yaml - 084% similarity]

<a href="https://commits.kde.org/sysadmin/repo-metadat" title="https://commits.kde.org/sysadmin/repo-metadat">https://commits.kde.org/sysadmin/repo-metadat</a>

Hi everyone,

To allow for Sysadmin to migrate the primary host for download.kde.org
and files.kde.org to another server (with significantly more disk
space) we'll need to make both of those read only for a period of time
this weekend.

During this period, it will not be possible to add/remove files to
those trees - which means projects will not be able to make releases.

To the knowledge of Sysadmin, this does not affect the release of any
project, however anyone who had plans should please contact us
immediately.

Regards,
Ben Cooksley
KDE Sysadmin

In 2011, something bubbled to SlashDot from this community.

<a href="https://tech.slashdot.org/story/11/08/07/2128222/KDE-Frameworks-50-In-Development" title="https://tech.slashdot.org/story/11/08/07/2128222/KDE-Frameworks-50-In-Development">https://tech.slashdot.org/story/11/08/07/2128222/KDE-Frameworks-50-In-De...</a>

TL;DR: what branching strategy to adopt for the KDE 5.x work, given
a wish to:
1) stay abreast of 4.x fixes/releases,
and 2) not make the mistakes of the 3.x to 4.x effort (whatever they were).

May I ask what actually happened re branching, merging, cherry picks
(back and forth) and all that, and what veterans think about it all
looking back?

This is really a question for posterity.

Hi all,

I'm announcing that Plasma Vault is in the review phase - you can get
it from kde:plasma-vault or with kdesrc-build plasma-vault.

Plasma Vault is a system for easy creation of encrypted data storage
(not for whole system encryption - we have distribution installers for
that).

It is consisted of:
- kded daemon that handles most of the logic
- Plasma applet to provide the UI

Features:
- Supports encfs and cryfs (more to come later)
- Vaults can be limited to certain activities (automatically closing
when you leave the activity it belongs to)

More info at [1] and [2]

Cheers,
Ivan

Hey,

just a short notice. From Feb to Aug. I won't be available very much at
computer, because I'll do a longer holiday in South France. I'll still will
answer mails, but not as fast as currently and I won't nearly do any
programming.

Best Regards,

sandro

14th January 2017. KDE today announces the release of KDE Frameworks 5.30.0.

KDE Frameworks are 70 addon libraries to Qt which provide a wide variety of·
commonly needed functionality in mature, peer reviewed and well tested·
libraries with friendly licensing terms.

Hi all,

It seems that my previous vocal complaints about system level /
serious impact dependency bumps on the CI system have gone completely
unnoticed by (some) members of our Community.

This was demonstrated earlier this week when components of Plasma
bumped their version requirements for XKBCommon and Appstream-Qt -
without even a thought about notifying Sysadmin or checking which
version the CI had, until their builds broke.

Neither of these is easy to fix at this stage, as the system base is
now too old to receive updates such as these.

Hi all,

Sysadmin is currently in the process of testing and evaluating
Collabora Online (CODE) as a replacement for notes.kde.org. We've
enabled this on share.kde.org.

It would be appreciated if people please test it out - anyone who is a
Developer, member of the e.V, or Visual Design Group should be able to
login on share.kde.org. Please send your feedback to this thread.

We've already figured out a process for exporting all data from
notes.kde.org, and will look to do this once initial testing is
finished - ideally this would happen a day or two after New Years.

Thanks,
Ben

In the old days it had kdelibs development discussion but not that that has
moved over to kde-frameworks-devel, waht's kde-core-devel for?

Can we kill it and move parts of it to kde-devel and other parts maybe to
release-team (like adding new software to releases and such)?

What do people that read this list think?

Cheers,
Albert