Re: [Development] API Change Review for 6.2
On Tuesday, 6 July 2021 08:29:04 PDT Giuseppe D'Angelo via Development wrote: > Hello, > > On 05/07/2021 12:54, Tuukka Turunen wrote: > > We have gotten review of the modules with larger number of changes > > progressing well, but a few modules are still without comments. > > > > With the Alpha out and Beta 1 soon ready to be released it is time to > > complete the API review so that we have the agreement upon what to do > > before release of Qt 6.2.0. > > Given the API review isn't finished, may I ask what are the criteria for > moving a release from Alpha to Beta to RC to full release? > > It used to be that > > Alpha = review the API; > Beta = review the implemetation; tl;dr: there's a one-step delay. Alpha releases are *published* so we can get feedback on the API. And while beta releases are *published* to get feedback on the implementation, that does not mean we can't get feedback on the API. We can still fix the API all the way up to the final release. The alpha release (singular) used to be "once feature complete", but we've been making multiple releases because, despite feature freeze, some things simply don't work properly at the feature freeze time. So we keep making them until one release does. Once we conclude the release is working sufficiently to get feedback on the implementation as well as API, we call it "beta". -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel DPG Cloud Engineering ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] API Change Review for 6.2
Hello, On 05/07/2021 12:54, Tuukka Turunen wrote: We have gotten review of the modules with larger number of changes progressing well, but a few modules are still without comments. With the Alpha out and Beta 1 soon ready to be released it is time to complete the API review so that we have the agreement upon what to do before release of Qt 6.2.0. Given the API review isn't finished, may I ask what are the criteria for moving a release from Alpha to Beta to RC to full release? It used to be that Alpha = review the API; Beta = review the implemetation; but evidently it's not that, and I missed the memo. 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 smime.p7s Description: S/MIME Cryptographic Signature ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Qt 6.2 Beta1 released
Hi all, We have released Qt 6.2 Beta1 today, please check the blog post at https://www.qt.io/blog/qt-6.2-beta-released Big thanks to everyone involved! br, Jukka Jokiniva Release Manager ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Mirror IRC channels on KDE's Matrix Instance
Hello, Since nobody refused to this decision, will contact the folks at KDE to start the process of mirroring the IRC channels into KDE's Matrix instance. Thanks everyone! Cheers On 6/28/21 12:51 PM, Cristián Maureira-Fredes wrote: Hello everyone, Context --- After the "Improve the contributor experience" session at the past Qt Contributors Summit, many ideas came out related to an overall improvement to the contribution experience, mainly focused on new people joining the Qt Project. One of the topics was Communication, from which we (qt project people) discussed together with some KDE folks and agreed that bringing the Qt and KDE communities closer was a good idea, mainly based on the good experience KDE has currently on the platform. We have a good opportunity to do this via a bridge from our newly created Libera.chat IRC channels, to KDE's Matrix Instance. During the QtCS, we tried this out, and mirrored the #qt-cs IRC channel to Matrix: https://go.kde.org/matrix/#/#qt-cs:kde.org and according to the people that participated in the session the experience was nice, and it might be worth to bridge all the other #qt-* channels on IRC. Read more about Matrix: https://matrix.org/ Read more about KDE's Matrix Instance: https://community.kde.org/Matrix Implications If you prefer IRC, it's totally fine, this change would only imply that you will get more people on IRC to interact with. If you want to move to Matrix completely, this change will enable you to stay in touch with folks on the IRC channels. Permissions work different on Matrix than IRC, but with the current list of moderators in the #qt- domain we can easily assign permissions to people on the Matrix channels accordingly. Let's keep the discussion of other communication platforms outside this thread, while they might be valid, it's out of the scope of this proposal. Question I would like to ask the Qt Project if you agree or disagree with the proposal to mirror all the #qt-* channels from Libera.chat to KDE's Matrix Instance. If we don't have unresolved disagreements, I'd say we can proceed with the mirroring Monday next week, but if there are concerns, I would prefer to address them first. Cheers -- Dr. Cristián Maureira-Fredes R Manager The Qt Company GmbH Erich-Thilo-Str. 10 D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Jouni Lintunen Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
