Confluence 6.10.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.10.0-rc1
Released 20 June 2018
No significant changes in this release candidate.
Highlights of 6.10.0-beta1
Released 13 June 2018
Read-only mode comes to Data Center
We know that work can't stop for maintenance windows, and for many organizations, it can be difficult to find time for planned maintenance. If you need to perform maintenance while Confluence Data Center is still running, or you're preparing to migrate to a new site, you can put your site into read-only mode to limit what users can do.
Everyone will be able to view pages and move around the site, but not create, edit, comment, or change things. This allows admins to make changes, safe in the knowledge that the treasure trove of information that keeps your team running, is still accessible.
From maintaining a read-only mirror while you upgrade, to acting quickly to mitigate the impact of a serious problem, read-only mode is there for you, when you need it.
On in an instant
You can enable read-only mode in the admin console. There's no need to stop or restart Confluence. Head to Administration menu , then General Configuration > Maintenance to check it out.
Get the message out
Keep everyone in the loop with a site-wide banner. It's quick and easy to customize the content of the banner to let people know why the site is read-only, and when you expect it to be available again.
You can even enable the banner independently, before you make your site read-only. This is a great way to warn your team of upcoming maintenance.
How does it work?
When read-only mode is enabled, we hide some parts of the UI (like buttons and actions), and block requests to create or edit. This means it doesn't matter whether the request is coming from an end user, an add-on, or via the API, we'll head it off at the pass.
Some operations may still write to your database, but for the most part, ordinary users will be unable to make any changes.
This feature is only available if you have a Confluence Data Center license.
Search improvements for everyone
In this release we've been improving the quality of search results by fixing some of the really annoying problems that get in way of you finding your work. Here's some of the highlights:
- Hyphens in file names no longer break search! Now you can search for "all-the-things.png" and find them too.
- Accents and special characters will now be ignored in search results. For example, searching "nino" will also return "niño".
- Spaces with titles that contain underscores now appear correctly when you filter the space directory by part of the space name. For example, entering "appreciation" in the filter will now happily return the Underscore_appreciation_society space.
- You can now specify Arabic or Persian as your indexing language. Changing the indexing language can improve search results if the majority of your content is in these languages.
Some of these fixes will only apply to newly created or edited content, or until you reindex your site. Reindexing can be time consuming in some sites, so we'll leave it for you to decide when the time is right for your site.
We're not done yet, so stay tuned for more search improvements over the next few releases. A huge thanks to all the customers who helped us with research and tried our proof of concept.
A new approach for resource-intensive tasks in Data Center
Confluence generates thumbnail images of files such as Office documents, so they can be viewed inline in the page, or in the preview. This can be very memory and CPU intensive, and the more complex the file, the higher the risk of out of memory errors.
In Data Center, to minimise the impact on the Confluence node, this is now handled in a sandbox, a seperate pool of processes, managed by Confluence.
You'll need to make sure that each Confluence node in the cluster has at least 2GB free memory to cater for the sandboxes. We plan to use this approach for other resource-intensive tasks in the future.
There's no change to the way this works in Confluence Server.
Supported platforms changes
In this release we've:
- added support for Microsoft SQL Server 2016
- upgraded Apache Tomcat from 8.0.x to 9.0.8
Infrastructure changes
Head to Preparing for Confluence 6.10 to find out about changes that will impact add-on developers.
Known issues
No known issues at this time.