On July 5, 2013, 2:23 p.m., David Faure wrote:
kio/kio/scheduler.cpp, line 766
http://git.reviewboard.kde.org/r/111335/diff/2/?file=167766#file167766line766
Please don't put this code in scheduler.cpp
I'm trying to properly split core and gui aspects of KIO in
On Monday, July 8, 2013 15:04:40 Àlex Fiestas wrote:
You can read all the proposal in:
http://community.kde.org/KDE_Core/ReleasesProposal
Neat ... some thoughts:
== On branching
this will be much easier for those who develop features in branches rather
than use master as a big developer free
On July 5, 2013, 2:23 p.m., David Faure wrote:
kio/kio/scheduler.cpp, line 766
http://git.reviewboard.kde.org/r/111335/diff/2/?file=167766#file167766line766
Please don't put this code in scheduler.cpp
I'm trying to properly split core and gui aspects of KIO in
On Wednesday 10 July 2013 01:25:06 Andras Mantia wrote:
On Tuesday, July 09, 2013 11:45:39 PM Martin Graesslin wrote:
* master is opened for feature development and will lead to Plasma
Workspaces 2 (or whatever the release will be called in the end).
Does this mean that kde-workspace in
On Wed, July 10, 2013 1:19 pm, Martin Graesslin wrote:
On Wednesday 10 July 2013 01:25:06 Andras Mantia wrote:
On Tuesday, July 09, 2013 11:45:39 PM Martin Graesslin wrote:
* master is opened for feature development and will lead to Plasma
Workspaces 2 (or whatever the release will be
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 to real
users (as opposed to testers/power users) and wait until there has been
a couple of bug fix releases. Until we ensure that
On Wednesday, July 10, 2013 02:12:41 PM David Jarvie wrote:
On Wed, July 10, 2013 1:19 pm, Martin Graesslin wrote:
On Wednesday 10 July 2013 01:25:06 Andras Mantia wrote:
On Tuesday, July 09, 2013 11:45:39 PM Martin Graesslin wrote:
* master is opened for feature development and will lead
On Mittwoch, 10. Juli 2013 15:34:43 CEST, Michael Jansen wrote:
Because of that it should be announced. BIG TIME.
I'd suggest to keep master as it is and develop PWv2 in a new branch.
Those who want to develop on or use it will hopefully find it and others can
continue to use master as it
On Tuesday 09 July 2013 21:57:51 Alexander Neundorf wrote:
On Tuesday 09 July 2013, Sven Brauch wrote:
I think Nuno's point is very interesting and worth thinking about. To
stick with the firefox example, since they started releasing every
ortography fix in the settings dialog as a new
On Tuesday 09 July 2013 16:12:35 Andras Mantia wrote:
Two point I want to mention:
1) working in a branch for kdepim is quite painful, as you need actually
work on branches of 3 (or sometimes 4) modules: kdepimlibs, kdepim-runtime,
kdepim (and akonadi). Keep them up-to-date, merge them at the
On Tuesday 09 July 2013 21:15:54 Ingo Klöcker wrote:
On Tuesday 09 July 2013 09:36:00 andrea diamantini wrote:
My idea about this concerns the way we let other people know aboout
new features. I usually read our feature plan (e.g.
http://techbase.kde.org/Schedules/KDE4/4.11_Feature_Plan).
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 to real
users (as opposed to testers/power users) and wait until
Hi, one of Debian's Qt/KDE packagers here.
Àlex Fiestas wrote:
On Monday 08 July 2013 20:35:22 Luca Beltrame wrote:
(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 openSUSE packages are
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 one.
Second one
Release frequency.
We have a giant quality problem. Distros won't ship a .0 release
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 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 one.
Second one
Release frequency.
We have a
A Quarta, 10 de Julho de 2013 13:18:57 Aaron J. Seigo escreveu:
== On branding and visual presentation
some have noted that faster release cycles would make it hard to implement
branding updates and artwork refreshes such as wallpapers. the answer to
that is simple: these efforts must not
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 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=
t the one=20
update.
this would ease the burdon on our release team (and by extension packag=
ers)=20
while also giving
A Quarta, 10 de Julho de 2013 17:43:38 você escreveu:
On Tuesday 09 July 2013 21:57:51 Alexander Neundorf wrote:
On Tuesday 09 July 2013, Sven Brauch wrote:
I think Nuno's point is very interesting and worth thinking about. To
stick with the firefox example, since they started releasing
On Wednesday 10 of July 2013 17:43:38 Àlex Fiestas wrote:
On Tuesday 09 July 2013 21:57:51 Alexander Neundorf wrote:
On Tuesday 09 July 2013, Sven Brauch wrote:
I think Nuno's point is very interesting and worth thinking about. To
stick with the firefox example, since they started
On 2013-07-10, Àlex Fiestas afies...@kde.org wrote:
I can't fight with distros, and I don't want to fight with them. If distros
need .5 .6 and .200 so be it, just they will have to do them themselves (and
I
hope we can make the process smooth so they can actually do it).
As has been said
On Wednesday 10 of July 2013 19:17:37 Luigi Toscano wrote:
The more you go down in the stack, the more you need stability, and no, it's
not true that with short release time the features will be smaller with
less bugs, because a feature could have been in development for a long
time, so it's
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=
t the one=20
update.
this would ease the burdon on our
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=
El Dimecres, 10 de juliol de 2013, a les 15:55:01, Thomas Lübking va escriure:
On Mittwoch, 10. Juli 2013 15:34:43 CEST, Michael Jansen wrote:
Because of that it should be announced. BIG TIME.
I'd suggest to keep master as it is and develop PWv2 in a new branch.
Those who want to develop
On Mittwoch, 10. Juli 2013 21:58:34 CEST, Albert Astals Cid wrote:
Those who want to develop on or use it will hopefully find it
and others can
continue to use master as it is. (And where important bugfixes etc. for
4.12 can go)
But there's not going to be a kde-workspace 4.12 as announced a
On Mittwoch, 10. Juli 2013 22:39:01 CEST, Scott Kitterman wrote:
I thought you said in the 3 month release cycle discussion that
every module
I think this discussion in unrelated to the new release cycle thread.
Frozen workspace and the question what to do with the branches in kde-workspace
On Wednesday 10 July 2013 22:39:29 Thomas Lübking wrote:
On Mittwoch, 10. Juli 2013 21:58:34 CEST, Albert Astals Cid wrote:
Those who want to develop on or use it will hopefully find it
and others can
continue to use master as it is. (And where important bugfixes etc. for
4.12 can go)
29 matches
Mail list logo
