[Development] frozen tickets on bugreports.qt-project.org in qt-mobility and qt-components

[Blasche Alexander]

--
Alex


> -----Original Message-----
> From: development-bounces+alexander.blasche=digia.com at qt-project.org
> [mailto:development-bounces+alexander.blasche=digia.com at qt-project.org]
> On Behalf Of Alan Ezust
> Sent: Monday, 20 January 2014 23:33
> To: deDietrich Gabriel
> Cc: development at qt-project.org
> Subject: Re: [Development] frozen tickets on bugreports.qt-project.org in qt-
> mobility and qt-components
> 
> 
> In the case of https://bugreports.qt-project.org/browse/QTCOMPONENTS-930
> Qt-Components has a gallery example, as does Qt Quick Controls.
> I had just reported a related ticket against the gallery example of qt quick controls,
> so i was going to add a comment "see related ticket:"
> Meego is still a "supported" platform, with Jolla and all, right?
> 
> On a related note, in the case of many open qt mobility/multimediakit bugs, they
> should be moved to qtmultimedia. Perhaps a group search/replacement is in
> order there?

Please feel free to shift them to Qt5 as you see fit. However please check that they still apply before you move them.
For some of my former Mobility modules I shifted applicable issues but left other issues as open inside the Mobility project. After all there are occasional users of old Mobility API's and they might have a use of those bugs. 

I might mark the QtMobility project as deprecated in Jira.

> On Mon, Jan 20, 2014 at 12:43 PM, deDietrich Gabriel
> <Gabriel.deDietrich at digia.com> wrote:

> 	As the header says on that page, QTCOMPONENTS is deprecated. Those
> tickets relate to an old set of components from the Nokia times. We keep them
> around for reference (although I don’t think any of that code is in Qt 5), and we
> should definitely close them (and by “we,” I mean anyone with the right
> superpowers).

I will close them tomorrow to give ppl time to reject today.

--
Alex