On Sunday 02 July 2017, David Faure wrote:
>
> I'd like to finalize the tagging today.
> With kirigami still having issues with translations, CI, and naming, I'd
> like to skip it for now and release it next month, unless there are strong
> reasons to do otherwise.
I'm fine with this as well
--
On Saturday 01 July 2017, David Faure wrote:
> On vendredi 30 juin 2017 15:16:17 CEST Marco Martin wrote:
> > Hi,
> > I have moved it, should be good to go.
> > one sidenote (hoping is not a problem) for historical reasons, the
> > tarballs were called kirigami2-version instead of just kirigami (or
On zaterdag 1 juli 2017 11:27:21 CEST Albert Astals Cid wrote:
> https://websvn.kde.org/trunk/l10n-kf5/templates/messages/frameworks/libkirig
> ami2plugin_qt.pot?revision=1492189&view=markup
>
> Disagrees with you
Ow, okay. I see, I only grepped for i18n, not for qsTr(), sorry for the noise!
> O
On 01/07/17 12:48, David Faure wrote:
> On vendredi 30 juin 2017 15:16:17 CEST Marco Martin wrote:
>> Hi,
>> I have moved it, should be good to go.
>> one sidenote (hoping is not a problem) for historical reasons, the
>> tarballs were called kirigami2-version instead of just kirigami (or
>> distrib
Il 02 luglio 2017 10:07:49 CEST, Rik Mills ha scritto:
>On 01/07/17 12:48, David Faure wrote:
>> On vendredi 30 juin 2017 15:16:17 CEST Marco Martin wrote:
>>> Hi,
>>> I have moved it, should be good to go.
>>> one sidenote (hoping is not a problem) for historical reasons, the
>>> tarballs were ca
Il 02 luglio 2017 09:55:48 CEST, David Faure ha scritto:
>On samedi 1 juillet 2017 13:48:28 CEST David Faure wrote:
>> On vendredi 30 juin 2017 15:16:17 CEST Marco Martin wrote:
>> > Hi,
>> > I have moved it, should be good to go.
>> > one sidenote (hoping is not a problem) for historical reasons,
On samedi 1 juillet 2017 13:48:28 CEST David Faure wrote:
> On vendredi 30 juin 2017 15:16:17 CEST Marco Martin wrote:
> > Hi,
> > I have moved it, should be good to go.
> > one sidenote (hoping is not a problem) for historical reasons, the
> > tarballs were called kirigami2-version instead of just
On vendredi 30 juin 2017 15:16:17 CEST Marco Martin wrote:
> Hi,
> I have moved it, should be good to go.
> one sidenote (hoping is not a problem) for historical reasons, the
> tarballs were called kirigami2-version instead of just kirigami (or
> distributions may have some problems in upgrading)..
https://websvn.kde.org/trunk/l10n-kf5/templates/messages/frameworks/libkirigami2plugin_qt.pot?revision=1492189&view=markup
Disagrees with you
Sent from Yahoo Mail on Android
On ds., jul. 1, 2017 at 9:02, Sebastian Kügler wrote: On
vrijdag 30 juni 2017 23:16:49 CEST Albert Astals Cid wrote:
On vrijdag 30 juni 2017 23:16:49 CEST Albert Astals Cid wrote:
> What happened to the "no new strings after the first two weeks" rule?
Kirigami doesn't have any translatable strings.
--
sebas
http://www.kde.org | http://vizZzion.org
El divendres, 30 de juny de 2017, a les 15:16:17 CEST, Marco Martin va
escriure:
> Hi,
> I have moved it, should be good to go.
Yeah let's do everything last minute, for sure translations will be moved fine
and all will be great.
What happened to the "no new strings after the first two weeks" r
Hi,
I have moved it, should be good to go.
one sidenote (hoping is not a problem) for historical reasons, the
tarballs were called kirigami2-version instead of just kirigami (or
distributions may have some problems in upgrading).. do release
scripts need to be adapted in some way?
On Fri, Jun 30,
What's the status with the move of Kirigami to frameworks?
Do we want it in 5.36 tomorrow?
AFAICS it's still in extragear/libs/kirigami in kde_projects.xml.
David.
On lundi 26 juin 2017 11:25:08 CEST Marco Martin wrote:
> On Sat, Jun 24, 2017 at 3:27 PM, David Faure wrote:
> >> the default styl
On Sat, Jun 24, 2017 at 3:27 PM, David Faure wrote:
>> the default style for QtQuickControlsStyle1 is "Desktop"
>> we could have called this style "Desktop" as well so all would have
>> aligned nicely, but that could be quite dangerous, as Qt coulddecide
>> any moment that they indeed want to do a
On Sun, Jun 25, 2017 at 8:44 AM, David Faure wrote:
> On samedi 24 juin 2017 11:15:25 CEST Ben Cooksley wrote:
>> Please check the new CI at https://build-sandbox.kde.org/ for the
>> current state of affairs.
>
> This doesn't appear to have kirigami at all?
Kirigami is currently in Extragear, and
On samedi 24 juin 2017 11:15:25 CEST Ben Cooksley wrote:
> Please check the new CI at https://build-sandbox.kde.org/ for the
> current state of affairs.
This doesn't appear to have kirigami at all?
--
David Faure, fa...@kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5
On Sun, Jun 25, 2017 at 1:27 AM, David Faure wrote:
> On samedi 24 juin 2017 11:52:22 CEST Marco Martin wrote:
>> > from requiring Qt 5.7.
>> > This Qt version difference creates an issue for the CI though, as can be
>> > seen at https://build.kde.org/job/kirigami%20master%20stable-kf5-qt5/
>>
>>
On samedi 24 juin 2017 11:52:22 CEST Marco Martin wrote:
> > from requiring Qt 5.7.
> > This Qt version difference creates an issue for the CI though, as can be
> > seen at https://build.kde.org/job/kirigami%20master%20stable-kf5-qt5/
>
> so it could be released as a framework anyways, good
> If i
whops, forgot cc to kde-frameworks, resending
On Sat, Jun 24, 2017 at 10:58 AM, David Faure wrote:
> On lundi 5 juin 2017 14:42:47 CEST Marco Martin wrote:
>> Hi all,
>> The Kirigami component set always was targeted to be eventually released as
>> a framework, ideally tier 1. since a framework mu
he requirements around Qt 4 and some other things have now been
sorted I intend to switch it over to become production in the next 24
hours.
>
>> i would like to propose to move Kirigami in
>> frameworks, to be relased in the main release cycle, and stop standalone
>> releases
hough, as can be
seen at https://build.kde.org/job/kirigami%20master%20stable-kf5-qt5/
> i would like to propose to move Kirigami in
> frameworks, to be relased in the main release cycle, and stop standalone
> releases from extragear.
>
> It strictly depends just from Qt stuff,
On Wed, Jun 21, 2017 at 6:22 PM, Jonathan Riddell wrote:
> On 21 June 2017 at 15:00, Marco Martin wrote:
>> As there were no replies for quite a while, i assume there are no
>> particular objections.
>>
>> so, how to proceed? what needs to be doe to do the actual move?
>
> Does it comply with the
On 21 June 2017 at 15:00, Marco Martin wrote:
> As there were no replies for quite a while, i assume there are no
> particular objections.
>
> so, how to proceed? what needs to be doe to do the actual move?
Does it comply with the policies (as much as they are relevant for QML)?
https://community
d as a
> framework, ideally tier 1. since a framework must depend at most from 2 Qt
> releases before the current one, it couldn't be released there yet.
> Now that Qt 5.9 is released, i would like to propose to move Kirigami in
> frameworks, to be relased in the main release cyc
move Kirigami in
frameworks, to be relased in the main release cycle, and stop standalone
releases from extragear.
It strictly depends just from Qt stuff, so should be tier 1 (at runtime it can
use optional styles that use features from Plasma, tough not having plasma
installed doesn't
25 matches
Mail list logo
