Release Notes 2.8-m2 ("Milestone 2")


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.

Confluence 2.8-m2 is a milestone development release for 2.8. This is a public development release (DR) leading up to Confluence 2.8. 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.

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.

Milestone releases have not been load- or stress-tested. So, for example, they 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.7.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 in this release

  • Velocity template engine upgrade

Confluence's velocity template engine has been upgrade from 1.3 to 1.5. This shouldn't mean too much to end users however there could be some compatibility problems with existing themes and plugins. Check this upgrade guide that we use internally as well:

  • File upload component upgrade

Pell multipart has been replaced with the Jakarta Commons Fileupload component to handle web browser file uploads. Again this won't have much impact on the Confluence experience but could cause some odd problems when attaching files to Confluence.

  • PDF space export

There has been some optimizations made the space PDF export which should result in less server memory usage during export

  • New GZIP compression filter

Confluence team have integrated a new GZIP compression filter to achieve more efficient downloads and page views. This is not currently enabled by default, so to test this with your plugin you need to turn it on in the management console. We are using it internally at Atlassian, and the performance improvement while browsing pages is quite substantial.

You can view the complete list of fixes and newly implemented features in JIRA. They contain all the issues resolved during development of 2.8, not just the ones fixed since the previous milestone.

Known problems

There are a few cosmetic UI problems related to space logos and to the login screen, none of them impact productivity. Notification mails are empty because of a Velocity macro bug.

Last modified on Jan 16, 2008

Was this helpful?

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