Il 09/12/20 09:13, Allan Sandfeld Jensen ha scritto:
1. Live with it or find a work around
2. Break BC after 6.0.0 (we have don that before, though only when accidently
breaking BC in a point release)
3. Break BC again "soonish", like after 6.2 or 6.5

Any other options?

These are not mutually exclusive, by the way. One thing is to break BC in 6.1 to address API/ABI problems found after 6.0 release -- if necessary, and we can't find reasonable workarounds, etc. -- , another thing is to have the leeway to break BC every now and then within Qt 6 lifetime.

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

Attachment: smime.p7s
Description: Firma crittografica S/MIME

_______________________________________________
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Reply via email to