On Saturday, July 23, 2011 04:41:05 AM Ben Cooksley wrote:
Hi,
I find what is proposed by Shaun to be acceptable, as the distinction
between the two is clearly defined. It still allows users to determine
the correct System Settings application to use to configure KDE
applications with what
On Sunday, July 24, 2011 05:07:19 PM Ben Cooksley wrote:
Dropping GNOME out of this, as it seems quite clear they aren't
interested in co-operating at all. Which is fairly typical for them,
they're insular and only care for themselves.
In any case, we need a short term solution to this.
On Sunday, July 24, 2011 05:52:08 PM Cornelius Schumacher wrote:
On Sunday 24 July 2011 Ben Cooksley wrote:
Dropping GNOME out of this, as it seems quite clear they aren't
interested in co-operating at all. Which is fairly typical for them,
they're insular and only care for themselves.
I
Thomas Zander zan...@kde.org wrote:
On Monday 25 July 2011 07.49.17 Scott Kitterman wrote:
I haven't seen anything in any mailing list posts that is nearly as
aggressive as knowningly reusing a name that was in use like
systemsettings.
Please don't assume that was an agressive act.
I can
On Saturday, August 06, 2011 09:32:02 AM David Faure wrote:
..
The next step is to backport the few bits of new api that went into master
and that application developers started using, into the 4.7 branch of
kdelibs. I'll work on that, but help is welcome too.
...
This plan seems to be
On Tuesday, August 09, 2011 07:05:53 PM David Faure wrote:
On Monday 08 August 2011 00:42:50 Scott Kitterman wrote:
On Saturday, August 06, 2011 09:32:02 AM David Faure wrote:
..
The next step is to backport the few bits of new api that went into
master and that application
On Wednesday, August 10, 2011 08:39:49 AM David Faure wrote:
On Tuesday 09 August 2011 19:26:17 Scott Kitterman wrote:
On Tuesday, August 09, 2011 07:05:53 PM David Faure wrote:
On Monday 08 August 2011 00:42:50 Scott Kitterman wrote:
On Saturday, August 06, 2011 09:32:02 AM David Faure
On Monday, August 15, 2011 05:31:26 PM Alexander Neundorf wrote:
5) Required cmake version
David noted that we (KDE) are very conservative with the required CMake
version, i.e. we still depend on CMake 2.6.4, which is more than a year
old. Me (Alex) noted
On Thursday, September 29, 2011 03:27:58 PM Markus Slopianka wrote:
On Donnerstag 29 September 2011 14:01:50 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.
Since almost exactly 2 years we (esp. the promo team) are
On Thursday, September 29, 2011 11:47:22 PM Albert Astals Cid wrote:
A Dijous, 29 de setembre de 2011, Scott Kitterman vàreu escriure:
On Thursday, September 29, 2011 08:01:00 PM Kevin Kofler wrote:
On Thursday 29 September 2011, Heinz Wiesinger wrote:
From what I remember from
On Thursday, September 29, 2011 11:47:55 PM Albert Astals Cid wrote:
...
That is actually Dirk's plan (or at least that is what i remember from the
Release Team BoF in Berlin).
...
Are the results of this BoF published anywhere?
Scott K
On Friday, September 30, 2011 04:15:51 PM Markus Slopianka wrote:
(As a side note I also think that KDE Applications should completely lose
their version number and get date-based versioning because any application
can get major new features at any time – see Dolphin 2.0 in SC 4.8.)
Today,
On Saturday, October 01, 2011 08:27:02 AM Martin Gräßlin wrote:
On Saturday 01 October 2011 00:12:05 Arne Babenhauserheide wrote:
Am Freitag, 30. September 2011, 10:07:27 schrieb Aaron J. Seigo:
will say Platform 4.7, Plasma
Workspaces 4.8 and application updates (or something along
On Saturday, October 01, 2011 08:38:09 PM Dario Freddi wrote:
On Saturday 01 October 2011 20:07:12 Stefan Majewsky wrote:
On Sat, Oct 1, 2011 at 7:33 PM, Andras Mantia aman...@kde.org wrote:
I can't comment on activities, never used them, nor feel the need to
use them. So this sounds more
On Sunday, October 02, 2011 08:37:58 PM Dario Freddi wrote:
On Sunday 02 October 2011 20:31:37 Martin Gräßlin wrote:
And that's now exactly the point: if you don't have any clue about what
is happening your I want to save power and not let the computer
decide might be much worse than what
On Sunday, October 02, 2011 09:28:42 PM Dario Freddi wrote:
No, sorry to say that again. There are two categories of people: those who
know what they are talking about and those who don't. Your understanding of
this categorization is coming from the fact that you didn't understand what
I am
Kevin Kofler kevin.kof...@chello.at wrote:
Andrea Diamantini wrote:
Ok, let's wait 18 months to see private browsing fixed. Going to
update
bug reports...
Try nagging distros to backport your (or your contributors') patches.
Unfortunately, it looks like trying to convince the kdelibs
On 11/15/2011 02:46 PM, Thomas Lübking wrote:
Am Tue, 15 Nov 2011 13:17:45 -0500
schrieb Scott Kittermank...@kitterman.com:
It is probably worth a discussion on packagers to share cross-distro
ideas about what kdelibs feature patches to ship with 4.8.
While Scott's suggestion to have a
On 11/15/2011 04:08 PM, Thomas Lübking wrote:
Am Tue, 15 Nov 2011 15:20:44 -0500
schrieb Scott Kittermank...@kitterman.com:
a) drain sources from KDE frameworks
Only if the people that would work on this would otherwise work on
KDE Frameworks. AFAIK, that's not the case.
If one wants a
On 11/16/2011 11:31 AM, Aaron J. Seigo wrote:
On Tuesday, November 15, 2011 16:28:21 Scott Kitterman wrote:
On 11/15/2011 04:08 PM, Thomas L�bking wrote:
If one wants a feature in future KDE versions and such fork wouldn't
exist, one would not add it at all rather than to the frameworks
On 11/17/2011 04:05 AM, Thomas Zander wrote:
On Thursday 17 November 2011 00.14.23 Scott Kitterman wrote:
the best way to deal with it is not to consider it a fork of kdelibs
but the next version of kdelibs (that's what it is) and help out with
it
I'd be interested if I could, but learning
On Wednesday, February 22, 2012 07:00:26 PM Martin Gräßlin wrote:
Am 22.02.2012 18:13, schrieb Laszlo Papp:
The suggestion remains: to allow everyone to edit and close bugs, as
is
apparently the case in some other bug trackers.
+1.
Worked fine on the MeeGo bugzilla for instance, I
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 Friday, June 15, 2012 01:05:44 PM Sebastian Kügler wrote:
Hi all,
During our sprint in Pineda de Mar, we sat down and thought about how our
release cycles relate to the structures in our software, we came up with the
following proposal we'd like you to consider and provide feedback about.
On Friday, June 15, 2012 01:05:44 PM Sebastian Kügler wrote:
Hi all,
During our sprint in Pineda de Mar, we sat down and thought about how our
release cycles relate to the structures in our software, we came up with the
following proposal we'd like you to consider and provide feedback about.
On Thursday, June 28, 2012 09:20:54 PM Thiago Macieira wrote:
On quinta-feira, 28 de junho de 2012 18.53.03, viv...@gmail.com wrote:
Il 28/06/2012 16:31, Thiago Macieira ha scritto:
On quinta-feira, 28 de junho de 2012 14.38.37, viv...@gmail.com wrote:
actually for stability and feature
On Sunday, July 01, 2012 11:08:43 PM Ivan Čukić wrote:
...
- 4.6 is desired for the features, but problematic since not all
current stable versions of distros sport this version (last to fall
into line - Slackware)
...
Debian Stable (Squeeze) is also 4.5 by default. The next version (Wheezy)
On Monday, July 08, 2013 03:04:40 PM Àlex Fiestas wrote:
Now that kde-workspace and kdelibs are going to be frozen (which in theory
means less work for everybody) I'd like to propose a new release schedule to
be applied starting with 4.12.
Basically the idea is to cut testing time and
On Monday, July 08, 2013 04:35:30 PM Àlex Fiestas wrote:
On Monday 08 July 2013 16:26:00 laurent Montel wrote:
No it’s not a good idea because nobody tests branch you can see pb that we
had when we merge akonadi branch (last big changes).
So no develop in branch will just create more bugs.
On Monday, July 08, 2013 04:59:50 PM Àlex Fiestas wrote:
On Monday 08 July 2013 10:40:21 Scott Kitterman wrote:
We've already experienced having some parts of the SC skip releases and it
was a real problem from a distribution perspective. Please, let's not do
it again.
KDE-PIM
Albert Astals Cid aa...@kde.org wrote:
El Dilluns, 8 de juliol de 2013, a les 11:25:42, Scott Kitterman va
escriure:
On Monday, July 08, 2013 04:59:50 PM Àlex Fiestas wrote:
On Monday 08 July 2013 10:40:21 Scott Kitterman wrote:
We've already experienced having some parts of the SC skip
On Tuesday, July 09, 2013 02:02:48 AM Aleix Pol wrote:
On Mon, Jul 8, 2013 at 3:04 PM, Àlex Fiestas afies...@kde.org wrote:
Now that kde-workspace and kdelibs are going to be frozen (which in theory
means less work for everybody) I'd like to propose a new release schedule
to
be applied
On Monday, July 08, 2013 09:55:28 PM Albert Astals Cid wrote:
El Dilluns, 8 de juliol de 2013, a les 20:35:22, Luca Beltrame va escriure:
(apologies for breaking your threading, but I'm not subscribed to k-c-d;
in
fact, please CC me with replies, thanks!)
Currently, the people working
On Tuesday, July 09, 2013 12:05:30 PM Àlex Fiestas wrote:
On Monday 08 July 2013 22:01:29 Andrea Scarpino wrote:
We don't just run a sed rule on each spec (pkgbuild, in my case) file. We
check for new dependencies (resp. dependencies not needed anymore), new
modules (resp. modules not part
On Tuesday, July 09, 2013 12:11:48 PM Àlex Fiestas wrote:
On Monday 08 July 2013 20:16:16 Scott Kitterman wrote:
For Kubuntu (also mostly volunteer effort), it took about two weeks to
package the 4.11 beta. For generating package updates for already
existing
packages, we have a script
Vishesh Handa m...@vhanda.in wrote:
On Tue, Jul 9, 2013 at 4:13 PM, Scott Kitterman k...@kitterman.com
wrote:
These all have to be test compiled, checked for new or missing
files,
checked for files that have moved between packages, checked for
license/copyright updates, etc.
I guess you
On Tuesday, July 09, 2013 12:52:04 PM Àlex Fiestas wrote:
On Tuesday 09 July 2013 06:43:48 Scott Kitterman wrote:
I want the point releases. The reasons for wanting them are for
consistency, marketing, and for distro policy releases its' much easier to
get a set of packages that are part
On Wednesday, July 10, 2013 06:08:04 PM Àlex Fiestas wrote:
On Wednesday 10 July 2013 13:22:20 Sune Vuorela wrote:
On 2013-07-09, Sune Vuorela nos...@vuorela.dk wrote:
So. first one.
Second one
Release frequency.
We have a giant quality problem. Distros won't ship a .0 release
On Wednesday, July 10, 2013 06:54:06 PM Àlex Fiestas wrote:
On Wednesday 10 July 2013 18:26:55 you wrote:
On Wednesday 10 of July 2013 18:08:04 Àlex Fiestas wrote:
On Wednesday 10 July 2013 13:22:20 Sune Vuorela wrote:
On 2013-07-09, Sune Vuorela nos...@vuorela.dk wrote:
So. first
On Wednesday, July 10, 2013 07:44:35 PM Martin Graesslin wrote:
On Wednesday 10 July 2013 17:13:11 Sune Vuorela wrote:
On 2013-07-10, Aaron J. Seigo ase...@kde.org wrote:
=3D=3D On scheduling mainenance releases
in a longer 4 month cycle, i=E2=80=99d cut that to 8 weeks and keep jus=
On Friday, July 12, 2013 05:27:53 PM Aaron J. Seigo wrote:
On Wednesday, July 10, 2013 14:23:24 Scott Kitterman wrote:
I've mentioned before in this thread, we're going to look into
providing tip of the stable branch packages that people can test so that
there is more testing before
On Monday, July 15, 2013 02:48:01 PM Albert Astals Cid wrote:
El Diumenge, 14 de juliol de 2013, a les 04:19:52, Inge Wallin va escriure:
I think keeping 6 months is a good
figure to ensure both reasonable turn-around *and* actual bugfixes of
versions being used in the real world.
It may
On Monday, July 15, 2013 09:00:27 PM Luca Beltrame wrote:
Àlex Fiestas wrote:
Now that kde-workspace and kdelibs are going to be frozen (which in theory
means less work for everybody) I'd like to propose a new release schedule
to be applied starting with 4.12.
Replying to the message
I wish I was there.
Scott K
Albert Astals Cid aa...@kde.org wrote:
Just as a reminder, we have the Release Team BOF tomorrow July 17 at
10:15 at
Room A2
Cheers,
Albert
El Dimarts, 16 de juliol de 2013, a les 14:38:47, Scott Kitterman va
escriure:
On Monday, July 15, 2013 09:00:27 PM Luca
On Thursday, July 18, 2013 01:19:12 AM Albert Astals Cid wrote:
El Dimecres, 17 de juliol de 2013, a les 07:37:16, Luca Beltrame va
escriure:
Albert Astals Cid wrote:
Just as a reminder, we have the Release Team BOF tomorrow July 17 at
10:15
at Room A2
Would it be possible to
Ben Cooksley bcooks...@kde.org wrote:
Hi all,
In order to improve the maintainability and cleanliness of the shared
dependencies the way they will be handled on the CI system will be
changing.
The nature of this change is that all projects which need a shared
dependency will now need to
defined the mailto
URL scheme).
- Scott Kitterman
On July 10, 2014, 8:40 p.m., Felix Geyer wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/119221
, but I'm still
sorting through the details. Upstream for PyQt refers to the configure.py for
QScintilla2 as a sample for how things should be done in the new world order
and it appears to determine it. I'll provide details shortly..
- Scott Kitterman
On July 15, 2014, 9:19 p.m., Raphael Kubo
or
# PyQt5 isn't relevant to the question (QScintilla does do this, but it's not
# germane).
pyqt = 'PyQt4'
if pyqt is not None:
pyqt_sip_dir = os.path.join(py_sip_dir, pyqt)
else:
pyqt_sip_dir = None
print(pyqt_sip_dir)
# prints /usr/share/sip/PyQt4
We should use something similar.
- Scott
On July 16, 2014, 1:42 a.m., Scott Kitterman wrote:
This is the method used in qscintilla2's configure.py (which upstream has
generally endorsed):
#! /usr/bin/python
import sys
import os
if sys.platform == 'win32':
data_dir = sys.prefix
else:
data_dir
On July 16, 2014, 1:42 a.m., Scott Kitterman wrote:
This is the method used in qscintilla2's configure.py (which upstream has
generally endorsed):
#! /usr/bin/python
import sys
import os
if sys.platform == 'win32':
data_dir = sys.prefix
else:
data_dir
On July 16, 2014, 1:42 a.m., Scott Kitterman wrote:
This is the method used in qscintilla2's configure.py (which upstream has
generally endorsed):
#! /usr/bin/python
import sys
import os
if sys.platform == 'win32':
data_dir = sys.prefix
else:
data_dir
On Thursday, April 23, 2015 10:55:17 PM Albert Astals Cid wrote:
El Dijous, 23 d'abril de 2015, a les 22:25:20, Valentin Rusu va escriure:
Hello,
Please be advised sysadmins moved kwallet-query to kdereview for your
constructive critics.
You may found more informations about it
On Monday, December 07, 2015 04:33:37 PM Thomas Lübking wrote:
> On Montag, 7. Dezember 2015 15:54:40 CEST, Luca Beltrame wrote:
> > Given you've said this multiple times, with my packager hat on I'll just
> > mention this: just don't make it harder *for us* to work just because
> > you're
On Thursday, April 07, 2016 12:16:58 AM Albert Astals Cid wrote:
> So my suggestion would be renaming pykde5.git to pykf5.git, and that means
> *only* KDE Frameworks 5 bindings would go in there, any other repo that
> wants to provide python bindings (say okular, marble or krita) should do
>
On Saturday, March 26, 2016 10:30:18 PM Shaheed Haque wrote:
> Hi all,
>
> I've given up on trying to get the twine2 PyKDE bindings generator
> working [1] because not only is the code there broken, but it seems a
> Sysiphusian task to maintain a C++ parser. Instead, a few evenings
> with clang
56 matches
Mail list logo
