The Qt Company has just announced Qt 6.0 Release Candidate 1 as what should be the second to the last test build ahead of the big Qt 6.0 toolkit release next month.

Qt 6.0 Release Candidate 1 has the latest batch of bug/regression fixes to the Qt6 code-base. The very basic Qt 6.0 RC1 release announcement can be read on the Qt development list.

Porting from Qt 5 to Qt 6 has been intentionally kept easy. There has been a conscious effort throughout the development of Qt 6 to maintain as much source compatibility with Qt 5 as possible. Still, some effort is involved in porting. This short post summarizes some of the steps required when porting to Qt 6.

In Qt 5 some of the classes already had existing replacements, and some classes got successors during the Qt 6 development phase. Therefore it might make sense to be able to compile your code with both the old and new Qt version. This can ensure that the amount of work where your code does not compile with either version is minimized, allowing your application or library to continue to work with Qt 5 and Qt 6. Another advantage could be that existing unit tests continue to work for most of the duration of porting, and regressions resulting from porting your code are easily distinguished from bugs introduced in Qt 6.

These are some answers to the Week 88 of the Perl Weekly Challenge organized by Mohammad S. Anwar.

The process of adopting a new governance model for the Perl project appears to be reaching an end; the new model is designed to look a lot like the one adopted by the Python project