> On 16 Aug 2019, at 19:02, Giuseppe D'Angelo via Development > <development@qt-project.org> wrote: > > Il 16/08/19 12:26, Lars Knoll ha scritto: >> As you know, Qt 5.14 will be branched pretty soon. After that I would expect >> that most new development work would start to be aimed towards Qt 6. As it >> looks right now, 5.15 will be a smaller release where we polish what we have >> in 5.14, and prepare some things for Qt 6. > > What's the proposed model for any source incompatible change landing in Qt 6 > that deserves a corresponding deprecation/compatibility mode/etc. in 5.15?
Here’s my proposal: * First do the deprecation in 5.15, document that it’ll go away in the commit message and make sure to CC the maintainer for the module about it in gerrit. * Then remove in dev once it’s landed and merged. * Document those in both the 5.15 and Qt 6 changelogs. Cheers, Lars > > Thanks, > -- > Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer > KDAB (France) S.A.S., a KDAB Group company > Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com > KDAB - The Qt, C++ and OpenGL Experts > > _______________________________________________ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
