If I may add a user's perspective to the discussion.
I know gift season is over, but here is what I (as a user) would ideally get:
1) Things get deprecated, including clear communicating when they are planned
to be removed (e.g. "to be removed in Qt 7" or "to be removed in Qt 8")
2) There is always at least one X.Y-release between deprecating and removing.
So if something is deprecated in the last version of Qt 6.x, it is removed in
Qt 8, not Qt 7
3) This also gives me time, as a user, to study deprecations, and write a
support ticket ("are you serious?") in the probably rare cases things would
really break the world for me
4) Offering Compat modules is welcome where it is feasible
That said, I welcome improving APIs, so I (as a user) am ready to accept a
moderate amount of pain. (Of course, you must, under no circumstances, ask the
people responsible for our release schedule...)
Kind regards
Robert
________________________________
This message and any attachments are solely for the use of the intended
recipients. They may contain privileged and/or confidential information or
other information protected from disclosure. If you are not an intended
recipient, you are hereby notified that you received this email in error and
that any review, dissemination, distribution or copying of this email and any
attachment is strictly prohibited. If you have received this email in error,
please contact the sender and delete the message and any attachment from your
system.
ANDRITZ HYDRO GmbH
Rechtsform/ Legal form: Gesellschaft mit beschränkter Haftung / Corporation
Firmensitz/ Registered seat: Wien
Firmenbuchgericht/ Court of registry: Handelsgericht Wien
Firmenbuchnummer/ Company registration: FN 61833 g
DVR: 0605077
UID-Nr.: ATU14756806
Thank You
________________________________
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
