[Development] [request] Creation a new QtSerialPort component into a Qt bug tracker

Knoll Lars Lars.Knoll at digia.com
Wed Jun 26 09:04:26 CEST 2013

I can do that, but I can unfortunately not migrate the open bugs to the new component (as I can't migrate across Jira projects). You'd have to create a new report for each of the open bugs in the Jira Qt project. If you're ok with that I'll remove the serial port component in  the playground project.


From: Laszlo Papp <lpapp at kde.org<mailto:lpapp at kde.org>>
Date: onsdag 26. juni 2013 04:11
To: Lars Knoll <lars.knoll at digia.com<mailto:lars.knoll at digia.com>>
Cc: Thiago Macieira <thiago.macieira at intel.com<mailto:thiago.macieira at intel.com>>, "development at qt-project.org<mailto:development at qt-project.org>" <development at qt-project.org<mailto:development at qt-project.org>>
Subject: Re: [Development] [request] Creation a new QtSerialPort component into a Qt bug tracker

Thank you.

Lars, could you please remove the "qtserialport" component from playground? We have just received a bugreport in there: https://bugreports.qt-project.org/browse/QTPLAYGROUND-31

On Tue, Jun 25, 2013 at 9:55 PM, Knoll Lars <Lars.Knoll at digia.com<mailto:Lars.Knoll at digia.com>> wrote:

On 6/25/13 8:39 PM, "Thiago Macieira" <thiago.macieira at intel.com<mailto:thiago.macieira at intel.com>> wrote:

>On terça-feira, 25 de junho de 2013 22.24.43, Denis Shienkov wrote:
>> Hello Qt developers.
>> At present the "main" component was QTPLAYGROUND, but recently users
>> began post bugs in "Qt" or "Other" components selection. Thus, it enters
>> some confusion...
>> Is planned a creation of a separate component for bug tracking of
>> QtSerialPort?
>Agreed, just call it "Serial Port".

Agreed as well. Here you go:


Development mailing list
Development at qt-project.org<mailto:Development at qt-project.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20130626/a29ffd84/attachment.html>

More information about the Development mailing list