Release Notes 2.0-RC2

Confluence 2.0-RC2 is the second release candidate for Confluence 2.0 (previously known as Confluence 1.5). It resolves almost 80 issues since the 1.5-RC1 release.

Who should upgrade?

Development releases are snapshots of the ongoing Confluence development process. We make them available for customers who are willing to risk an unpolished release in order to have early access to new features. Developer releases are not suitable for running on production systems.

If you want to be running the most stable and most reliable version of Confluence, you should stick with the official, numbered releases.

Upgrade Procedure

Upgrading Confluence should be pretty easy. If you are upgrading from Confluence 1.4 or higher, you can find instructions here. We strongly recommend that you backup your confluence.home directory and database before upgrading!

If you are upgrading from Confluence 1.3.x or earlier, be sure to read the upgrade instructions in the Confluence 1.4 release notes.

Important Notice

If, after you have upgraded Confluence, the "Recent Changes" list on the dashboard is empty, this may be because you need to re-build your site's search index. You can do this under Administration → Content Indexing → Rebuild Search Index

Important Notice 2

If, after you have upgraded Confluence and you find the page breadcrumbs do not show the page's parents correctly, log into your site as administrator, then visit http://yoursite.example.com/admin/permissions/rebuild_ancestor_table.action (substituting your own site's URL, obviously) to rebuild the ancestor table (this will be fixed for the final release.

Downloads

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

New Features in Confluence 2.0-RC2

The 2.0-RC2 has largely concentrated on fixing bugs and polishing existing features. If you are upgrading from Confluence 1.4 or earlier, you should read the 1.5-DR2 Release Notes for a description of the major new features in Confluence 2.0.

Consult JIRA for the full list of issues resolved for 2.0-RC2.

type key summary assignee reporter priority status resolution created updated due

Unable to locate JIRA server for this macro. It may be due to Application Link configuration.

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