Confluence 3.2 has reached end of life
Check out the [latest version] of the documentation
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 public development release ('milestone') leading up to Confluence 3.3, which will probably ship in mid June 2010. 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?
Please note the following
- Development releases are not safe — Development releases are snapshots of the ongoing Confluence development process. As such:
- While we try to keep these releases stable, they have not undergone the same degree of testing as a full release.
- Features in development releases may be incomplete, or may change or be removed before the next full release.
- No upgrade path — Because development releases represent work in progress, we can not provide a supported upgrade path between development releases, or from any development release to the eventual final release. Thus, it is possible that you will not be able to migrate any data you store in a Confluence development release to a future Confluence release.
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 (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 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 databases and application servers. 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 from Confluence 3.2.x to this release. We strongly recommend that you backup your Confluence home directory and database before upgrading!
Downloads
All development releases are available from the development releases page on the Atlassian website.
Gadgets & Office Team
Gadgets in the Macro Browser
Want to embed one of those fancy new JIRA gadgets into your page? This has become really easy with the new Macro Browser integration. Just have a look in the "External Content" category to find available gadgets. Confluence comes with the Confluence QuickNav gadget by default, but the administrator can add as many gadgets as you like.
Configure your JIRA gadgets in the Macro Browser
You can now configure your JIRA gadgets using the macro browser. Just pick a JIRA gadget from the Macro Browser, configure it and add it to your Confluence page or blog post.
Office 2007 support
We've fixed a couple of minor issues with the Word 2007 integration. But the really good news is that we've started working on PowerPoint 2007 support! Nothing to see yet, but stay tuned.
Dialogs Team
The new image browsing dialog has been restyled and as a bonus now works in new pages and blogs.
Engine Room
The Confluence REST plugin (prototype API) has now been enabled for this milestone. In addition to spaces (in previous milestone) we now have an API for viewing Confluence content (pages, blogs, comments) with page children expansion supported.
Some very basic documentation can be found here: Prototype REST API
Bugfix Team
Fixed multiple bugs .
Misc
Faster editor load
With a few improvements we have made to the way we load TinyMCE, it should appear faster across all the browsers.
This is an Agnes Ro 20% production