Milestone release advisory

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.

Overview

Milestone 1 is a fairly minor step from a user perspective, but since there are a number of changes that could potentially impact plugin development we wanted to get it to you as soon as we could. Read on for the changes as described directly by the developers.

Infrastructure Changes

Various changes to aid plugin development

  • All ContentEntityObjects can now be commented on
  • UserStatus now optionally belongs to a space
  • Custom space types
  • Bandana 2.0
    • Custom context objects
    • Key enumeration
    • Item removal
    • Custom serialisation

Deprecation notice

DWR has been deprecated as of 3.3-m1. Support for the client side Javascript proxies has been moved into the Confluence Legacy Web Resources plugin which is going to be disabled by default (it currently isn't - automatically disabling the DWR web resources when updating Confluence will be in Milestone 2). If you need any of the following web resources you have to enable this plugin:

  • DWR framework
  • DWR Javascript proxies for label (add, remove, suggest) or editor operations (heartbeat, draft saving, editor preferences)

Slimmer Blog View

The blogs view has been modified as shown in the screen shot below.



Changes shown in the screenshot:

  • The old calendar has gone. It's been replaced by a sidebar that simply lists the month and all the blogposts for that month, and allows you to scroll between the months that have blogposts in them.
  • The view's been streamlined - we've gotten rid of some of the unnecessary information on the page.
  • In a global space, the view you get in Browse > Blogs has the user's picture attached to the blog for easier identification.

And the additional changes not visible:

  • The dates have been internationalised - until now they were stuck in English.
  • The Browse > Blogs view allows you to see older/newer posts, not just the most recent 15.

All Implemented Issues

Issues Implemented in 3.3-m1  (${entries.size()} issues)

Key Summary Status
Refresh

  • No labels

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.