Preparing for Confluence 6.5
This documentation is intended for Confluence developers who want to ensure that their existing plugins and add-ons are compatible with Confluence 6.5.
Release candidate 1 - 23 October
This release candidate contains minor fixes and improvements, including the editor resource restructuring known issue described below.
Beta 1 - 16 October
In this beta:
- Start and stop scripts are now available to help you run Synchrony standalone for Data Center. You'll find the new scripts in your Confluence
<install-directory>/bin/synchronydirectory. Simply move the scripts to your Synchrony node, insert the values for your environment and you're ready to go. Head to Configuring Synchrony for Data Center in our EAP documentation to find out more.
- Applinks upgrade to 5.4.1
For a complete run down of all the features and changes in this beta, head to our Confluence 6.5.0-beta release notes.
Known issue: Editor resource restructuring
We restructured some of the editor resources in 6.5. These are meant to be backwards and forwards compatible; however, we found an issue if you are loading the Confluence Editor manually in your plugin. Some features might not be working correctly, such as Links or Mentions. We're on it and this will be fixed for RC and Final. See CONFSERVER-53917.
Milestone 22 - 9 October
In this milestone:
- New system add-on to provide targeted in-app notifications in Confluence (this add-on also recently shipped in Jira 7.4). Notifications will be predominantly targeted to administrators and will provide information on new Confluence versions and upcoming license renewals.
- Synchrony upgraded to 2.1.x
Milestone 16 - 3 October
We've made some changes to how you configure your database in the setup wizard:
- The option to use a datasource will only appear if you have already configured a datasource in the server.xml.
- You can now enter database details in a simple form, or can choose enter your own connection URL (which was the previous method).
- We've added a few more checks to make sure the database is configured up correctly and is using the correct character set, collation, isolation level etc to help customers avoid future problems.
We've also completed a few library and other upgrades including:
- Tomcat upgraded to 8.0.46
- Jodatime upgraded to 2.9.9
Milestone 12 - 25 September
There are no notable changes in this milestone.
Milestone 8 - 18 September
We've made some changes to our Support Tools. When you upgrade Confluence to 6.5.0-m08 or later:
- the following plugins will be uninstalled:
- Confluence Required Health Checks Plugin
- Confluence Healthcheck plugin
Support Healthcheck Plugin
- Support Tools Plugin
- a new plugin called Atlassian Troubleshooting and Support Tools will be installed.
You can find the new Troubleshooting and support tools in the admin console under Troubleshooting and support tools. The functionality of the plugin (health checks, log analyzer, support zip etc) has not changed.
Milestone 4 - 12 September
This is our first public milestone for Confluence 6.5. Not much has changed yet, but keep an eye on this page, as we'll be releasing a milestone every week in the lead up to Confluence 6.5.
- Improved email threading. Confluence will group all the email notifications about changes to a specific page together. Other notifications such as sharing a page, or requesting access to a page are not grouped.
New Azure deployment template for Confluence Data Center
Our new Azure deployment template is ready for you to take for a test drive. The template makes provisioning a new Confluence Data Center cluster in Microsoft Azure simple. Head to Getting started with Confluence Data Center in Azure to find out how it works.
We've still got some work to do, including an app for the Azure marketplace, but we'd love your feedback on our work so far, so raise an issue to tell us what you think.