[Development] Feature freeze next Tuesday
lars.knoll at qt.io
Wed Sep 2 10:38:19 CEST 2020
Pure ABI changes are no problem until 6.0 is released.
Source incompatible changes are something we should restrict to where required now, and you’ll need to be prepared to follow up with commits in other modules.
> On 2 Sep 2020, at 10:29, Иван Комиссаров <abbapoh at gmail.com> wrote:
> Is it still ok to break abi after the feature freeze? I’d like to move some private methods to the protected interface of the QAbstractItemView and make those virtual (basically, most Private slots). I found it quite inconvenient that I cannot call some code before/after the reaction to the signal from the model.
> Dunno if I will find time to do that, but I wonder if this is still possible. Should be a pretty simple refactor.
> Иван Комиссаров
>> 26 авг. 2020 г., в 08:47, Lars Knoll <lars.knoll at qt.io> написал(а):
>> Hi all,
>> This is just a gentle reminder that feature freeze for Qt 6 is approaching very quickly now. We’ve had a round of checks inside the Qt Company regarding how ready the teams are. All in all it looks relatively good, so we’ll keep the feature freeze at the 1st of September.
>> There are three areas that have asked for an exception to the freeze to finish things that are still pending:
>> * In QtCore, the Q*Iterables in qmetatype/qvariant
>> * Across Gui/Declarative/QuickControls the input system
>> * The new desktop styling for Qt Quick Controls
>> * The new property system (see separate mail; most likely it won’t need an extension to the freeze date)
>> Those areas can finish the required changes to those subsystems beyond the feature freeze.
>> I would hope that there are no other exceptions required. If something is not done, but can easily be pushed to 6.1, you know what to do. If anybody knows about something else that can’t be pushed please talk to me, so we can figure out what to do about it.
>> Development mailing list
>> Development at qt-project.org
More information about the Development