[Development] Add-ons: Removing obsolete API in the same major version

Konstantin Ritt ritt.ks at gmail.com
Tue Oct 29 19:19:19 CET 2013


Maybe simply deprecate that API with a respective macro?

Regards,
Konstantin


2013/10/29 Thiago Macieira <thiago.macieira at intel.com>

> On terça-feira, 29 de outubro de 2013 18:01:34, Laszlo Papp wrote:
> > Hi,
> >
> > I am about to deprecate some API in QtSerialPort after some discussion
> with
> > others. The target is 5.2 for this, but I would like to know if we can
> > remove that API or revamp it without considerations in 5.3 and later.
>
> You can remove in Qt 6.0.
>
> If you want to remove in 5.3, you'll need to change the library soname. We
> don't have a provision for that in the buildsystem. I urge you not to go
> this
> route.
>
> > Perhaps, this would not be possible for essentials before Qt 6, but what
> is
> > the policy for add-ons? Can exceptions be made in there?
>
> See above.
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel Open Source Technology Center
>
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20131029/67cb3706/attachment.html>


More information about the Development mailing list