Confluence 6.9.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.9.0-rc1
Released 1 May 2018
Our tray tables are up, our seats locked in the upright position, and Confluence 6.9 is ready for takeoff.
There are no significant changes in this release candidate.
Highlights of 6.9.0-beta1
Released 24 April 2018
More control over your editing experience
Based on your feedback, we've made some changes to the editor footer. A new ellipsis menu gives you the option to:
- preview the page
- view all changes since the page was last published
- revert back to the last published version
- delete the page, if it has never been published.
When you click the Close button, we'll no longer ask you whether you want to keep or discard changes, as this was confusing for many people. Now, the changes are always kept - you'll need to go to> Revert to last published version if you want to discard them.
Simpler proxy and HTTPS setup
Many customers choose to run Confluence behind a reverse proxy, often with HTTPS enabled. To make setup and configuration easier, we've added more sample connectors to the
server.xml file. There are now connectors for:
- HTTP without a reverse proxy (default)
- HTTP with a reverse proxy
- HTTPS without a reverse proxy
- HTTPS with a reverse proxy
It's simpler to set up, and easier to get right, first time.
We now support running Confluence in an IPv6 environment. In most cases there is nothing you need to do, however there are few known issues and limitations that you need to be aware of:
- Must allow IPv4 traffic
Some parts of Confluence, including the Universal Plugin Manager and Atlassian Troubleshooting and Support Tools, need to be able to connect to IPv4 sites, such as Atlassian Marketplace.
- AWS RDS does not yet support IPv6
For this reason, our CloudFormation template and Quick Start, will continue to provision an IPv4 VPC.
- The editor doesn't recognize IPv6 addresses
When you paste or type a raw IPv6 address into the editor, it won't automatically be treated as a link. Pasting the domain name of an IPv6 site will work just fine.
- Some database drivers don't reconize IPv6 addresses
When connecting Confluence to a database, you may need to use the fully qualified domain name, rather than the raw IPv6 address, of your database server.
- Problems with collaborative editing in Firefox
Confluence must be able to connect to Synchrony for collaborative editing to be available. If you set a custom value for synchrony.host, it must be a fully qualified domain name, and not a raw IPv6 address. If you're using Confluence Data Center, see the information below on what you need to do.
If you're running Confluence Data Center, and have collaborative editing enabled, you'll need to:
- Start Synchrony with
-Dhazelcast.prefer.ipv4.stack=false(simply uncomment this line in the latest version of the start-synchrony script)
- Specify a fully qualified domain name for the Synchrony URL, not the raw IPv6 address.
Read-only mode update
As mentioned in Preparing for Confluence 6.9, our new read-only mode feature will not be available in Confluence 6.9. We hope to make it available in the next release, and will keep you posted on any further changes.
Supported platforms changes
No changes planned for 6.9.
Head to Preparing for Confluence 6.9 to find out about changes that will impact add-on developers.
No known issues at this time.