odftoolkit-0.13.0

[lawern]

Hi there,

Are there any plans for when the next release will come out?
For the last few years you have always released a new version at the end of the year.

Thanks for your great work and best regards
Lars

[svanteschubert]

Hi Lars,

My initial plan was to do a release as usual, but I had too much on my plate, and the paid work overruled the pro-bono work.
But I asked for sponsors—without a response yet—and would love to finish the refactoring and improve code generation to finally release a 1.0 release. If this is the case, we will do a release as is (tip of master), followed by the one with improved generation.
Otherwise, I hope/guess to find some spare time to do at least a release before FOSDEM, which I will attend.

Have a great new year!
Svante

[svanteschubert]

I discussed this issue by phone with @olira and he suggested investing more into the automation of the release process and using something similar as

• https://github.com/semantic-release/semantic-release

Tested the semantic-release tooling a bit this evening, in the freshly cloned ODF toolkit repo root, I called:

1. npx semantic-release
2. npx semantic-release --dry-run true -b master -r https://github.com/tdf/odftoolkit

Post Scriptum:
To run npx you need to have Nodejs installed, which I manage by nvm, see https://michael-kuehnel.de/node.js/2015/09/08/using-vm-to-switch-node-versions.html as there are so many specific versions you need to have - like in Python a virtual environment as Anaconda is easier

The above still tries to push to the repo, which is not what I would call a "dry-run" ;-)
Likely they are "only" doing GitHub releases, but at least the release notes are being generated from the commit messages and semantic versioning is derived...

In addition, we have more steps to automate - perhaps in GitHub actions like

• JavaDoc generation
• Maven release - see also https://github.com/embesozzi/java-semantic-release
• copying latest release odftoolkit.org
• automated testing of the release

But it seems worth investigating further in this direction and when doing the next release think about how to automate the steps next time.
In case someone is curious the latest release notes are here: https://tdf.github.io/odftoolkit/release-guide.html

Does anyone use the tooling above or has any experience or suggestions?

I started to search a bit and also found further background material, like
https://medium.com/@luca.motta1993/semantic-version-and-how-to-integrate-semantic-release-in-a-gitlab-ci-cd-pipeline-for-a-java-235b0f91dedb

Cheers,
Svante

[svanteschubert]

Please take todays SNAPSHOT release as a beta for the upcoming release, aside of using SNAPSHOT in your pom.xml (there should be a new download today) you might download the JARs manually from:

1. https://oss.sonatype.org/content/repositories/snapshots/org/odftoolkit/odfdom-java/0.13.0-SNAPSHOT/odfdom-java-0.13.0-20250108.141044-10-jar-with-dependencies.jar
2. https://oss.sonatype.org/content/repositories/snapshots/org/odftoolkit/xslt-runner/0.13.0-SNAPSHOT/xslt-runner-0.13.0-20250108.141044-10-jar-with-dependencies.jar
3. https://oss.sonatype.org/content/repositories/snapshots/org/odftoolkit/odfvalidator/0.13.0-SNAPSHOT/odfvalidator-0.13.0-20250108.141044-10-jar-with-dependencies.jar

Godspeed!
Svante

[lawern]

Hi Svante,

Thank you so much!

Unfortunately, I only got around to testing today.

However, the JUnit tests for our application have all run successfully and the processed ODS files are all OK.