On 26/04/14 23:32, Kevin Ottens wrote:
Please get back to us when you're done checking your framework, if you get
any
issue or if something is unclear.
Alex Merry:
- kdesignerplugin
- kimageformats
- kmediaplayer (porting aid)
All checked.
Alex
On Sunday, April 27, 2014 12:32:25 AM Kevin Ottens wrote:
No maintainer:
- krunner (porting aid)
I'm willing to maintain krunner.
--
Vishesh Handa
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
On Tuesday 29 April 2014 12:40:16 Vishesh Handa wrote:
On Sunday, April 27, 2014 12:32:25 AM Kevin Ottens wrote:
No maintainer:
- krunner (porting aid)
I'm willing to maintain krunner.
Please add vhanda to the maintainer key in the metainfo.yaml file then.
Regards.
--
Kévin Ottens,
On 26 April 2014 23:32, Kevin Ottens er...@kde.org wrote:
John Layt:
- kunitconversion
The only thing left is the move of KCurrencyCode back to kdelibs4support.
I've now done up patches, but I'm once again bamboozled by Reviewboard and
post-review and feel like a total idiot. I should just
On 29/04/14 13:48, John Layt wrote:
On 26 April 2014 23:32, Kevin Ottens er...@kde.org
mailto:er...@kde.org wrote:
John Layt:
- kunitconversion
The only thing left is the move of KCurrencyCode back to
kdelibs4support. I've now done up patches, but I'm once again
bamboozled
On 29 April 2014 14:16, Alex Merry alex.me...@kde.org wrote:
You are working on a separate branch as that wiki page suggests, right?
It wouldn't surpise me if using the --parent=master option from the
master branch gave you no changes.
I've tried both from the local master branch and a
On 29/04/14 14:35, John Layt wrote:
Using rbt post has the same result, but at least has more verbose
error messages:
One or more fields had errors (HTTP 400, API Error 105)
path: error: unable to find 1db2612bdc625b7267d31ce773ecfdcddc6ae045
fatal: git cat-file
On Wed, Apr 30, 2014 at 1:45 AM, Alex Merry alex.me...@kde.org wrote:
On 29/04/14 14:35, John Layt wrote:
Using rbt post has the same result, but at least has more verbose
error messages:
One or more fields had errors (HTTP 400, API Error 105)
path: error: unable to find
On Sunday 27 April 2014, Kevin Ottens wrote:
Marco Martin:
- kdeclarative
- plasma-framework
I think it's pretty fine on my part, i'll take another review on the metadata
files.
one thing I think i need are toplevel bugzilla products for each framework,
right?
(if so i'll open a sysadmin
Hello,
On Monday 28 April 2014 13:32:08 Marco Martin wrote:
On Sunday 27 April 2014, Kevin Ottens wrote:
Marco Martin:
- kdeclarative
- plasma-framework
I think it's pretty fine on my part, i'll take another review on the
metadata files.
one thing I think i need are toplevel
Hi,
Should we create a new component in bko, or we can rename the existing one
(kactivities - frameworks-kactivities)? (I did the former, but wanted to
check)
The same question for the revboard - should the repository be renamed to
frameworks-kactivities?
The only thing that I'm having issues
Hello,
On Monday 28 April 2014 16:32:41 Ivan Čukić wrote:
Should we create a new component in bko, or we can rename the existing one
(kactivities - frameworks-kactivities)? (I did the former, but wanted to
check)
Whatever works for you.
The same question for the revboard - should the
On Monday 28 April 2014, Kevin Ottens wrote:
Martin Klapetek did that for all frameworks a while back. All the
frameworks related products are prefixed with frameworks-. Looks like
your modules got moved after that and so are indeed missing. You think
right, you need to add them to bugzilla.
On Monday 28 April 2014 16:32:41 Ivan Čukić wrote:
Hi,
Should we create a new component in bko, or we can rename the existing one
(kactivities - frameworks-kactivities)? (I did the former, but wanted to
check)
The same question for the revboard - should the repository be renamed to
On Monday 28 April 2014 18:13:44 Marco Martin wrote:
On Monday 28 April 2014, Kevin Ottens wrote:
Martin Klapetek did that for all frameworks a while back. All the
frameworks related products are prefixed with frameworks-. Looks like
your modules got moved after that and so are indeed
Hello framework maintainers,
As you know we're getting near the final release. If we don't hit a critical
issue, we'll release the final early June. Before that, we'll have a second
beta on May 4th, and we'd like it to look as close to the final as possible.
That's why I'm sending you this
16 matches
Mail list logo
