1.0.0-beta-4 release is coming closer

The beta-4 release is cooking since 3 months now. It is taking a long time, and longer than expected. But we are now getting closer. With beta-4 we have purged JavaEE remainings and transitioned fully to JakartaEE.

Why does it take so long?

  • this was a massive refactoring
  • the refactoring had many implications on the integration tests
  • we were investigating flaky tests in deep

Now we have to make sure that everything is stable again. If you have the chance, test out the latest nightly builds. Once we feel safe enough we will perform the release.

2 Likes

If there are no objections I would schedule the beta-4 release for this Wednesday May 7th evening. Please use the last chance to test against the latest stable build and raise your voice for the case you find something blocking.

The integration tests are now running green with all distributions and against h2 and PostgreSQL each night.

We are now preparing the final steps before the release. I did some housekeeping marking all issues and PRs with [milestone 1.0.0-beta-4].(GitHub Ā· Where software is built).

The latest builds were not published to docker, as our runner was EOL for some time. Raised a PR to fix it, but from a Docker point of view there were no current builds for quite some time:

1 Like

We updated our product backoffice.plus on our staging and dev systems to beta-4 and now doing full development and qa with it. Weā€˜re going to rollout to our customerā€˜s production systems when beta-4 is released and we didnā€˜t find any blocker until then.

Tomorrow we should have our new builds. We should smoke-test them, although basic integration tests are already performed on building the images.