Release Notes 3.0-rc1 ("Release Candidate 1")


On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Hi everyone,

we are approaching the 3.0 release date. We have built our first release candidate, and we hope to turn this into the final release unchanged soon.

There have been a few changes since the last two betas: The translations are now up to date, more icons have been added to the macro browser, and we have tweaked a few screens, like the profile page. And of course we have fixed dozens of bugs (see JIRA URLs below). We are very pleased with the quality of the release and we are currently not aware of any showstoppers or critical issues. Chances are that the final release will be just a rebranded RC, however you should still not use the RC on production systems, since we still have some final testing planned. We encourage you to use it for staff training purposes and for your upgrade testing though, since no more UI changes or changes to the upgrade process are scheduled.

Milestone release advisory

For testing use only

Do not use this release to upgrade your production systems.

This release is a public development release ('milestone') leading up to the next Confluence major release. 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.

In supplying milestone releases, our aim is 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 all of our milestone releases even have been performance tested for a while.

However, since our milestones releases are timeboxed (that is, they are 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 that are scheduled to be fixed in the next milestone, or completely new bugs unknown even to us.

Additionally, we have not completed our performance testing and compatibility testing for all supported databases and user management systems. So, for example, a milestone release may behave well on a small installation but show severe problems when subjected to many users.

Upgrade Procedure

Follow the normal upgrade instructions to upgrade your test instance to this release. We strongly recommend that you backup your Confluence home directory and database before upgrading!


All development releases are available from the development releases page on the Atlassian website.

Issues resolved between Beta2 and Beta3:
Issues resolved between Beta3 and RC1:

Thanks for your feedback so far, it has helped us track down a few bugs, which will result in a smoother upgrade for everyone!

The Confluence Team

Last modified on May 28, 2009

Was this helpful?

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