Closed ShalokShalom closed 2 years ago
@ShalokShalom You are not wrong. But this project lost a bit of structure and vision since @ogoffart is focusing on other projects.
I got a bit carried away because I needed to optimize compile time as much as possible. So my branch is now C++20 and Qt 6.2.4+ only. But I have fixed some issues with Qt6.3+ and also full W_BINDABLE support.
One way would be to make a 1.3 release with the old prerequisites Qt 5+ and C++14. And add a 2.0 branch with C++20 and Qt 6.2.4+ to move on? Frequent releases are difficult because this project has no funding, so we rely on spare time participants.
My major concern right now is that, we have no good approach for QML_ELEMENT. (See #83) Without that I see no long term future for Verdigris. Unfortunately right now nobody seems to be willing to fund this risky development.
But let me know if my release strategy is worth the effort.
And add a 2.0 branch with C++20 and Qt 6.2.4+ to move on?
makes a lot of sense to me! I don't think there's a lot of people who would simultaneously
My major concern right now is that, we have no good approach for QML_ELEMENT.
I don't really use QML anymore, can't help with this sorry :/
One way would be to make a 1.3 release with the old prerequisites Qt 5+ and C++14. And add a 2.0 branch with C++20 and Qt 6.2.4+ to move on?
Sounds awesome
A 1.3 release at this point makes total sense, thanks to all the contributors
Wonderful ❤️
Considering the significant amount of contributions since 1.2, that happened in 2019, I suggest a new version to be released here.
And considering that there are already two other issues who raise awareness about missing released, I also suggest a frequent release schedule.
Does anyone love to sign up for this?