Confluence 6.12.0-beta Release Notes
Development releases are not production ready. Development releases are snapshots of the ongoing Confluence development process. While we try to keep these releases stable, they have not undergone the same degree of testing as a full release, and could contain features that are incomplete or may change or be removed before the next full release.
No upgrade path. Because development releases represent work in progress, we cannot provide a supported upgrade path between development releases, or from any development release to a final release. You may not be able to migrate any data you store in a Confluence development release to a future Confluence release.
Atlassian does not provide support for development releases.
Issues with this beta?
Please raise an issue to tell us about it.
Highlights of 6.12.0-rc1
Released 24 September 2018
No significant changes in this release candidate.
Highlights of 6.12.0-beta1
Released 19 September 2018
Confluence 6.12 is jam-packed with goodies that make administering a big, Confluence Data Center site easier.
Have a Confluence Server license? Stay tuned! We've got some really great search improvements coming in the not too distant future, that we know your users are going to love.
Simpler Synchrony setup for Data Center
Synchrony is the engine that powers collaborative editing in Confluence. Data Center admins can now choose to let Confluence manage Synchrony (as in Confluence Server), or continue to run Synchrony in its own cluster.
Which setup is right for you?
If you want a simple setup, and virtually no maintenance, then allowing Confluence to manage Synchrony for you is definitely the way to go.
If you're happy with your current setup, or if you need to ensure the editor is highly available, you can continue to run a standalone Synchrony cluster. The choice is yours.
How does it work?
In your current setup, we use the
synchrony.service.url property to tell Confluence where to find your standalone Synchrony cluster.
Now, if you start Confluence without this property, we'll automatically spin up a Synchrony process for you on the same node. As Confluence communicates with Synchrony via the Synchrony proxy, you don't even need to open the Synchrony port.
Take a peek at the architecture.
Because Synchrony is managed by Confluence, it's automatically upgraded when you upgrade Confluence. No more manual upgrades.
Switching is simple
Keen to try it out? Making the switch is very straightforward. Learn how to migrate from a standalone Synchrony cluster to managed Synchrony.
Take the worry out of PDF exports in Data Center
In Confluence 6.10 we introduced the idea of a "sandbox" (now known as the "external process pool") for handling memory and CPU intensive tasks, like document conversion.
In this release we've turned our attention to PDF exports, which we know can be problematic in some big sites. All PDF Export requests are now handled by the external process pool.
The conversion to PDF is now handled page by page in Data Center, so if there's a problem, we can tell you exactly which page is the culprit. Often it can be as easy as simplifying or excluding the offending page, and re-trying the export.
For admins, we've also improved error reporting in the logs, to help you get to the bottom of why some spaces are difficult to export.
Minimise the impact on your organisation
Because PDF exports are handled outside of Confluence, if things go wrong, the worst that can happen is the PDF export request fails. There's no impact to other users, and no additional load on Confluence. The days of a memory-hungry PDF export being able to cause an out of memory error that affects your entire Confluence site are over.
Learn more about PDF export in Confluence Data Center.
Supported platforms changes
We plan to drop support for PostgreSQL 9.3 with the release of Confluence 6.13.
Head to Preparing for Confluence 6.12 to find out about changes that will impact add-on developers.
No known issues at this time.