Confluence 5.6-Beta3 Release Notes

22 August 2014

Atlassian presents Confluence 5.6 Beta 3. This release is a snapshot of our work in progress, primarily focused on allowing Confluence users to see the new features in advance. Beta releases also give add-on developers an opportunity to test and fix their add-ons in advance of an official release.

Downloading this Confluence release

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.

Highlights of Confluence 5.6-Beta 3

This beta release contains a fix for  CONF-34565 - Counting license consuming users does not scale Resolved , which impacted performance in instances with a large number of users. 

See Confluence 5.6-Beta2 Release Notes for full details of the features in this beta. 

Giving feedback

We'd love your feedback so please:

  • Feel free to comment on this page with your feedback, or
  • Send us your comments via the 'Got Feedback' option in the header of your EAP Confluence site.

Upgrade notes

Follow the usual upgrade instructions to upgrade your test site to this release. If you are upgrading using the clustered artifact, some extra steps apply (see below). 

Shared home directory for clustered installations

We have introduced the concept of a shared home directory for clustered installations. All cluster nodes will now need to be configured with a path to a directory that is shared between all nodes.

(warning) The following upgrade steps only apply to existing clustered installations

Follow the normal upgrade procedure, but execute the following steps immediately after shutting down the existing cluster:

  1. Create a directory that is visible to all cluster nodes in the same path.

  2. Shut down the cluster.

  3. Edit confluence.cfg.xml in the home directory of each node and add a new property called confluence.cluster.home with the path of the shared directory as the value. For example:

    <property name="confluence.cluster.home">/yourpath/confluence-shared-home</property>
  4. Move all the files/directories from a home directory on one node to the new shared home directory except for the following: 

    • config
    • confluence.cfg.xml
    • index
    • temp
    • bundled-plugins
    • plugin-cache-*
    • plugins-cache
    • plugins-osgi-cache
    • plugins-temp

     Remove the moved files/directories from the home directories on all other nodes.

  5. Continue to follow the normal upgrade procedure. 

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport