Release Notes 2.3-DR2
Confluence 2.3-DR2 is the second public development release leading up to Confluence 2.3. Development releases are a snapshot of our work in progress, allowing our customers 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.
This development release is being made available specifically for Confluence plugin developers. The changes to the Confluence API discussed below mean that many plugins will need to be updated to work with Confluence 2.3.
For all production use and testing of Confluence, please use the latest official release.
This release should not be used for testing a clustered deployment; the clustering user interface is not yet complete.
Follow the normal upgrade instructions to upgrade from Confluence 2.2.x to this release. We strongly recommend that you backup your confluence-home directory and database before upgrading!
If you are upgrading from Confluence 2.1.x or earlier, be sure to read the upgrade instructions in the Confluence 2.2 release notes.
All development releases are available from Development Releases on the Atlassian website.
Things to look out for
- The Tangosol Coherence jars included in this DR are now fully licensed.
- The API for retrieving historical versions of content has changed.
Architecture changes between Confluence 2.3-DR1 and 2.3-DR2
Content history API changed
getPreviousVersions method of
ContentEntityObject has been removed, because it was insanely inefficient as soon as a piece of content started having lots of versions. It has been replaced with the following methods on the
ContentEntityObject getPreviousVersion(ContentEntityObject ceo); ContentEntityObject getNextVersion(ContentEntityObject ceo); ContentEntityObject getOtherVersion(ContentEntityObject ceo, int version); /** * Get a VersionHistorySummary for all previous versions of a ContentEntityObject, starting with the current * content. * * @param ceo the entity object to return the version history of * @return the full version history of that object, as VersionHistorySummary objects. */ List getVersionHistorySummaries(ContentEntityObject ceo);
VersionHistorySummary class defines a limited set of Content data that is relevant to viewing version histories.