Hi Turbine Devs, Before the holidays a short reminder for our community, what's be next:
Turbine release is in preparation. If you have any considerations you want to share please do it! 😊 That said, I hope we could finish the release end of January or in February, if all remaining problems could be tackled (currently still some Javadoc errors) .. What comes into my mind, is - Torque-5.2 which is not yet released would be more in line with the current future release of Turbine. Should we wait for a Torque release? We may speed up this release as the Turbine PMC and community partially share membership (to my knowledge 😉) .. Generally I think Torque is still suitable as a simple ORM tool, with some inherent limitations and improvable capabilities in schema -> sql generation, no migration process, etc., but still it is IMO appropriate and easy to use for simple use cases. If starting a new project, even if the project gets more mature, it supports a lot still. Any effort to change this, may be considered and supported .. - Do we need more tests? Some packages show quite low coverage. N.b. to see the coverage, if building the site, keep in mind using a Java version below Java 18 (add -Djacoco.skip=false) - else jacoco coverage build will be skipped (changed to the last stable jacoco build, which supports Java 21, is already done in last snapshot of parent pom). - Need we change the version from 5.2 to 6.0, because of Java 11 baseline? This will have the follow up to check for version changes in wiki (https://cwiki.apache.org/confluence/display/TURBINE) and site.Currently, the announcement on the wiki start page is that Turbine v5.2 has Java 11 baseline, and v6 will have java 17 or may be 21 baseline? - More caveats or reminders ? Thanks for the support to all of us! 😉 Best regards and happy holidays! Georg
