Meelogic Atlassian Blog

Confluence 7.0 release notes

✓ Clean up Synchrony data automatically

✓ Improve geo-performance with CDN support

✓ Be better prepared for upgrades

✓ Move your site to the Cloud

✓ Gearing up for future success

 

Welcome to Confluence 7

It’s been almost three years since Confluence 6.0 was released and has changed the way we work together. Since then, Atlassian has expanded its data center offerings, introduced enterprise releases to help you manage your upgrade cycle, and targeted end-user search and editing issues.

With Confluence 7.0, Atlassian continues to invest in the future of Confluence by providing solutions to geospatial performance challenges, better upgrade planning tools, and new management tools to best meet the unique needs of your business for years to come.

As a platform version, it also includes the technical foundation to prepare us for future performance and scalability improvements and allows us to continue to build a solid set of capabilities to meet the needs of administrators and end users in large enterprises.

Improve geo-performance with CDN support

For DATA CENTER

Geographic distance has a measurable impact on page loading times, so it is important to reduce this effort as much as possible if you have teams in multiple time zones. Do not allow geography to slow down your team. A Content Delivery Network (CDN) can help reduce frustration for distributed teams.

The new CDN feature for data centers allows you to deliver static content (such as JavaScript, CSS and fonts) from servers closer to your users, resulting in faster page load times. For example, if your Confluence Data Center Server (Origin, see screenshot) is located in Germany, a CDN can improve page loading speed for users in Rio de Janeiro because static resources are provided by an edge server in Brazil. At its test sites, Atlassian has seen a significant reduction in network traffic and CPU usage, and improved its Apdex scores by up to 15%.

To set it up:

  1. Use our template to spin up an AWS CloudFront distribution, or create an account with the CDN vendor of your choice.
  2. Update your load balancer and firewall to allow the CDN to reach your site.
  3. In Confluence, provide the CDN URL and enable CDN support.

Only static assets (such as JavaScript, CSS, and fonts) are cached. Pages, attached files, and personal data like avatars, are still served from your origin server.

Don’t want to open your site to the public internet? No problem, you can deploy your own caching servers, instead of using a third-party CDN.

Clean up Synchrony data automatically

For SERVER DATA CENTER

If you have a particularly busy Confluence site, you may have noticed that your database has gained a bit of weight since the introduction of collaborative editing. This is because Synchrony, the engine that powers collaborative editing, records every keystroke to keep editing sessions in sync. A great indicator of top-notch team collaboration, but bad news for your database.

Two new scheduled jobs will help keep this data under control:

  • The soft eviction job runs regularly, and proactively cleans up any Synchrony data that’s no longer required. This will keep your Synchrony database tables from growing too large over time.
  • A hard eviction job is available for when you need to remove data more aggressively, for example if you’ve deleted a number of pages and need to make sure personally identifiable information contained in them is also removed from Synchrony. It’s disabled by default, but there when you need it.

Be better prepared for upgrades

For SERVER DATA CENTER

It is well known that upgrades can require a lot of planning and preparation, so Atlassian has added some additional features to make it easier.

The new upgrade preparation planning tool combines all the necessary instructions in one place. Your Confluence website is analyzed, some checks are performed and an upgrade guide tailored to your instance and upgrade path is created.

Head to  > General Configuration > Plan your upgrade to check it out.

Best news? If you’re running Confluence 6.5 or higher, you can use this new tool to upgrade to Confluence 7 – just upgrade the bundled Troubleshooting and Support Tools application to the latest version.

Atlassian has also introduced a new reporting feature to make the post-upgrade experience even smoother. After a successful upgrade, you will see the status of your applications and application links and highlight any important changes that could affect your systems or users.

Access the report at any time from  > General Configuration > Latest upgrade report.

Move your site to the Cloud

For SERVER DATA CENTER

Some improvements have been made to the Cloud Migration Assistant for Confluence. This app is invaluable if your team is considering moving to the Confluence cloud.

The Migration Assistant application now also works for the Data Center Deployment Option. This means you can move your data center version of Confluence to the Atlassian Cloud at your own pace. The application now also supports user and group migration, giving you complete control over your migration.

 

Gearing up for future success

For SERVER DATA CENTER

Platform releases like this often mean major and remarkable changes to Confluence. Although the changes mentioned above may seem pretty insignificant at first glance, they open up a huge potential for major improvements that will help your team get the job done in Confluence.

  • Atlassian platform and third party library upgrades 
    We upgraded many of the Atlassian maintained libraries, and several important third-party libraries including jQuery, Guava, and Spring framework. This helps us leverage recent improvements, and move quickly if vulnerabilities are found in these libraries in future.
  • AUI 8 upgrade
    We upgraded the Atlassian User Interface library to version 8. This update only has a handful of visual changes, but sets us up for future improvements.
  • Removing deprecated code
    Over the years we’ve deprecated a large number of code paths and libraries, but although deprecated, they remained available in the code. This means it was still possible to rely on superseded technology. We’ve now removed much of the code deprecated prior to Confluence 6.0. By doing this, all apps must to switch to newer, recommended methods which will improve the overall health of Confluence and its apps