On Sun, 2024-01-07 at 13:12 +0000, [email protected] wrote: > About timeline: I would say do the migration after the next release. But > when migrated to PyQt6 we IMHO should wait some months until the next > release. If you have Issues that need to released asap or quit early > then we should wait with the migration.
Let's stick to our plan to prepare a release mid of January and apply time-boxing (what I can't fix won't be released), then we focus on the Qt6 version. Perhaps we can relax the idea of a pure Qt6 release a little bit since BiTs in CLI/backend are clearly separted from the GUI/App part so we could keep fixing these and release them together with the Qt6 release. > > I have still some open issues that would require small changes in the > > Qt5 GUI parts, eg. > > No problem. Decide on how urgent the issues are and when you want to > release them. Qt6 migration can be done early or later when ever the > other parts are ready. OK. See my answer above above _______________________________________________ Bit-dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/bit-dev.python.org/ Member address: [email protected]
