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
