-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plan for new release 5.2.0 #2576
Comments
Doesn't KVIrc use even numbers for stable releases? Thus it should be 5.2.0. |
Correct, 5.2.0. |
Shall we go for a "beta1" like 5.1.1, push it as a prerelease and ask feedback from bug tickets? |
Yeah, would not hurt
…-------- Исходное сообщение --------
6 дек. 2023 г., 12:52, ctrlaltca написал:
Shall we go for a "beta1" like 5.1.1, push it as a prerelease and ask feedback from bug tickets?
—
Reply to this email directly, [view it on GitHub](#2576 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AACPLZA7W6K24JAOT3YJSYDYIBTCVAVCNFSM6AAAAABAJGW366VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBSHAYTKMZSGA).
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
So, a little recap from the last few days. Since beta1, a couple of problems have been detected:
Beta2 was released with these fixes included. |
Update: beta3 released at https://github.com/kvirc/KVIrc/releases/tag/5.2.0-beta3
The new beta adopted the name "Quasar"; this name was already a candidate as noted in cmakelists.txt. The new artwork has been introduced in #2584 |
Update: no new reports of crashes since beta1.
#2590 is ready to be merged when CI goes green, 5.2.0 tagged etc.. |
i don't suppose qt6 on windows is a blocker for this, but just in case someone wants to look at that before release: qt 6.6.1 from vcpkg
the unicode stuff is due to qt6 using -utf-8 in the command line which needed a change in the cmakelists due to: cl : Command line error D8016 : '/source-charset:utf-8' and '/utf-8' command-line options are incompatible |
The error is about KviHeapObject, that is a workaround for windows memory management, and definitely needs proper testing. Qt6 on windows currently is completely untested. |
Released, closing. |
I guess it's about time to plan for a new release.
The 5.0 release contains a lot of known bugs, even crash bugs, thta have been fixed since a long time in master.
It could be 5.0.1, but a lot of nightlies already use that version, so i guess 5.1.0 would be more appropriate.
What blockers do we want to fix before drafting the release?
The text was updated successfully, but these errors were encountered: