In addition, we need per-version profiles. People will want to say "I
need to be compatible with Qt 6.14, but I want to adopt all best
practices up to that".
Sounds like a distinction without a difference. What are you thinking of here?
We may declare now that it's best to avoid AutoText and codify that in
some opt-in mechanism. Users will write code against that and develop
their application with, say Qt 6.14. After 6.14 is released, we'll
figure out that we should also get rid of Qt::Foozle and invoke the same
mechanism for this. Then the person with their application built on 6.14
will still want to avoid AutoText, but the application will still rely
on Qt::Foozle's old behavior and it will take a while to change that.
They'll want our behavior-breaking changes "up to" Qt 6.14, but no newer
ones. Only if we allow such a thing they can update to Qt 6.15 in a
timely fashion.
best regards,
Ulf
--
Development mailing list
[email protected]
https://lists.qt-project.org/listinfo/development
