This week we released a beta for Confluence 7.8. There are changes in this release that may directly affect 3rd-party apps, including a significant change to the embedded H2 database which will affect your development environments, automated tests, and anywhere else you might be using the embedded database.
New in 7.8
To find out what’s in this release, check out the Confluence 7.8 beta release notes.
Download the beta from our site to start testing your app for compatibility with the changes. Be sure to take a look at our Preparing for Confluence 7.8 guide to find out what you need to do to make your app compatible. We’ll update that page regularly, so keep an eye on it to see any changes.
The Atlassian Confluence team
If you have contacts in release management could you put some attention on CONFSERVER-60251 and Confluence Docker Images: we need a generic "eap" tag ?
It would be easy for partners to keep test servers up to date with the latest EAP version if there were an “eap” tag in the the Confluence docker hub. I think that Atlassian intended to have an “eap” tag but whoever is releasing those docker images may have forgotten about that step.
For example, to update my test server to this new beta release I edited my docker-compose.yml
and what I would like to do is use the “eap” label that Atlassian says they use, but the person who is publishing the images to docker hub isn’t using the label. If the “eap” label was in use all we’d have to do is restart our container to get the latest EAP version, we wouldn’t need to know the magic label “7.8.0-m37” or “7.8.0-beta1” or whatever.
Hi @TureHoefner, I think you’re right, and this step may have been lost or missed from our release process. I’ll raise it with our release champ today. Thanks for letting me know about the problem.
The Confluence 7.13 EAP release has not been put on docker hub (so it’s not available via the ‘eap’ tag).
I’m following up with Nathan about it in the 7.13 EAP announcement: Confluence 7.13 Long Term Support release EAP available now
The 7.12 EAP was available via the ‘eap’ tag in docker so it has been used recently. If there is a release workflow or process document maybe this needs to be added to it?