On Monday 10 February 2014 15:43:13 Marco Martin wrote:
On Monday 10 February 2014, Ivan Čukić wrote:
the above points should be done..
only thing, in kactivities frameworks should still be merged in master
(Ivan, would this be ok?)
Fine by me :) (even more than 'fine')
ok.
i
On Tue, February 11, 2014 20:59:24 David Faure wrote:
On Monday 10 February 2014 15:43:13 Marco Martin wrote:
On Monday 10 February 2014, Ivan Čukić wrote:
the above points should be done..
only thing, in kactivities frameworks should still be merged in master
(Ivan, would this be
On Saturday 08 February 2014, David Faure wrote:
* OK if I run astyle-kdelibs in both, to harmonize coding style?
(drawback: it makes forward-porting changes from 4.x harder)
+1 if you can do it.
+ Can you add both to http://community.kde.org/Frameworks/List?
This includes figuring out who
the above points should be done..
only thing, in kactivities frameworks should still be merged in master
(Ivan, would this be ok?)
Fine by me :) (even more than 'fine')
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
On Monday 10 February 2014, Ivan Čukić wrote:
the above points should be done..
only thing, in kactivities frameworks should still be merged in master
(Ivan, would this be ok?)
Fine by me :) (even more than 'fine')
ok.
i suppose kdesrc-build has to be updated beforehand tough to pick up
On Thursday 06 February 2014 23:32:11 David Faure wrote:
On Wednesday 05 February 2014 22:42:00 Michael Palimaka wrote:
On 02/03/2014 08:17 PM, David Faure wrote:
Any new module that should be added to this release, compared to TP1?
I see that plasma-framework.yaml says tier 3, is that
On Saturday 08 February 2014 10:31:10 David Faure wrote:
* it's not under frameworks/ in the projects.kde.org hierarchy. Shall we
move it?
* it declares itself to be version 2.0.0. Can I change that to 4.96.0 like
all other frameworks?
Ping? It's now or never, for alpha1 :)
On Saturday 08 February 2014 10:55:25 Marco Martin wrote:
On Saturday 08 February 2014 10:31:10 David Faure wrote:
* it's not under frameworks/ in the projects.kde.org hierarchy. Shall we
move it?
* it declares itself to be version 2.0.0. Can I change that to 4.96.0
like
all
On Saturday 08 February 2014 10:59:19 David Faure wrote:
On Saturday 08 February 2014 10:55:25 Marco Martin wrote:
On Saturday 08 February 2014 10:31:10 David Faure wrote:
* it's not under frameworks/ in the projects.kde.org hierarchy. Shall
we
move it?
* it declares itself
On Saturday 08 February 2014 11:36:26 Marco Martin wrote:
On Saturday 08 February 2014 10:59:19 David Faure wrote:
On Saturday 08 February 2014 10:55:25 Marco Martin wrote:
On Saturday 08 February 2014 10:31:10 David Faure wrote:
* it's not under frameworks/ in the projects.kde.org
Also, kactivities is the only framework that still uses a branch named
frameworks.
Can we switch to master = kf5 and KDE/4.13 for the current master, assuming a
4.13 release of it is planned? [otherwise what do we do with master?]
The only commit that is in master and not in 4.12 is this one
On Saturday 08 February 2014 12:44:48 David Faure wrote:
* plasma-framework depends on kactivities which is also not a proper
framework. Shall we make it one and release it together with the others?
It needs a bit of updating in the cmake stuff (it has too many of the
usually toplevel stuff
On Saturday, 8. February 2014. 13.26.41 you wrote:
On Saturday 08 February 2014 12:44:48 David Faure wrote:
* plasma-framework depends on kactivities which is also not a proper
framework. Shall we make it one and release it together with the others?
It needs a bit of updating in the cmake
On Saturday, 8. February 2014. 12.58.53 David Faure wrote:
Also, kactivities is the only framework that still uses a branch named
frameworks.
Can we switch to master = kf5 and KDE/4.13 for the current master, assuming
a 4.13 release of it is planned? [otherwise what do we do with master?]
I
On Saturday 08 February 2014 14:13:40 Ivan Čukić wrote:
On Saturday, 8. February 2014. 12.58.53 David Faure wrote:
Also, kactivities is the only framework that still uses a branch named
frameworks.
Can we switch to master = kf5 and KDE/4.13 for the current master,
assuming
a 4.13
more and more places - and especially all of the frameworks themselves.
Ok, I'm game for the branch switch. Is there any documentation on how/what
should be done to the cmake parts?
p.s.
Since then, kdelibs got splitted, so as I said, KF5 stuff is master in
The thread in question is from
On Saturday 08 February 2014, David Faure wrote:
* plasma-framework depends on kactivities which is also not a proper
framework. Shall we make it one and release it together with the others?
It needs a bit of updating in the cmake stuff (it has too many of the
usually toplevel stuff like
El Dissabte, 8 de febrer de 2014, a les 16:32:04, David Faure va escriure:
On Saturday 08 February 2014 14:13:40 Ivan Čukić wrote:
On Saturday, 8. February 2014. 12.58.53 David Faure wrote:
Also, kactivities is the only framework that still uses a branch named
frameworks.
Can we
On 02/03/2014 08:17 PM, David Faure wrote:
Any new module that should be added to this release, compared to TP1?
Should I include attica?
Any version number that should be upgraded in the modules themselves? I
realize now that it's all called 5.0.0 everywhere already. The packages are
Any new module that should be added to this release, compared to TP1?
Should I include attica?
Any version number that should be upgraded in the modules themselves? I
realize now that it's all called 5.0.0 everywhere already. The packages are
properly numbered, but not the cmake variable
On Monday 03 February 2014 10:17:49 David Faure wrote:
Any new module that should be added to this release, compared to TP1?
Should I include attica?
Since this question keeps popping up, let's integrate it. It should also be
added to the list: http://community.kde.org/Frameworks/List
Also,
21 matches
Mail list logo
