Release Notes 2.10-m4 ("Milestone 4")


On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Do not use this release to upgrade your production systems.

For all production use and testing of Confluence, please use the latest official release.
This release is a milestone development release for 2.10 ("Two Ten"). This is a public development release (DR) leading up to Confluence 2.10. Development releases are a snapshot of our work in progress, allowing our customers and especially plugin-developers to see what we're up to.

Who should upgrade?

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.

Our milestone releases aim to provide plugin developers with an opportunity to see the latest changes in the code.

Each milestone release has passed all our automatic tests, and has been used for one week on our official internal Confluence server. Most of the issues solved have been reviewed too, and usually milestone releases even have been load- and performance-tested for a while.

However, since our milestones releases are timeboxed (i.e. they get released every two weeks, no matter how far we have come implementing features and bugfixes), there is always a chance that we have new known bugs, which are scheduled to be fixed in the next milestone, or completely new bugs unknown even to us.

Additionally, our performance-testing and compatibility testing for databases and application servers is not done to the full extent. So, for example, a milestone release might behave well on a small installation but show severe problems when subjected to many users.

Upgrade Procedure

Follow the normal upgrade instructions to upgrade from Confluence 2.9.x to this release. We strongly recommend that you backup your confluence-home directory and database before upgrading!


All development releases are available from Development Releases on the Atlassian website.

Issues resolved or improved in this release

TinyMCE upgrade complete

  • Color Text, Insert Emoticons and Custom Character are now back in the editor!
  • Fullscreen mode is also back and even better. It no longer pops up in a new window, but enlargens the editor in the current page you are editing.

Quick Navigation polish and performance improvements

  • performance significantly better than m3
  • can handle concurrent requests up to 30 users without breaking a sweat (on medium datasets) - this should address the timeout issues people have been having


  • New build of JIRA Issues macros. Bug-fixes, but new feature: all RSS and Email version of the macro will be static, and not require javascript or Ajax.
  • Content Filtering Macros: contentbylabel and blogposts have a new, SearchAPI v2 backend.
    • All existing parameters should continue to work
    • New, standard set of parameters for various kinds of filtering
  • Content Filtering macros: new {recently-changed} macro, which is a reimplementation of {recently-updated}. All existing recently-updated params should work, with the addition of the new standard params listed above. Will eventually replace {recently-updted}.
  • Added an optional whitelist for the RSS macro and the HTML-include macro.
Last modified on Nov 8, 2016

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.