Documentation for Confluence 5.4.
Documentation for Confluence OnDemand and earlier versions of Confluence is available too.

Skip to end of metadata
Go to start of metadata

Outdated page

Icon

These are not the release notes you are looking for

This page is outdated, but has high Google ranking (smile)

Please refer to the official Confluence 3.1 release notes over here.

Milestone release advisory

For testing use only

Icon

Do not use this release to upgrade your production systems.

For all production use and evaluation of Confluence, please use the latest official release.

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?

Please note the following

Icon
  • Development releases are not safe. Development releases are snapshots of the ongoing Confluence development process. For that reason:
    • 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 cannot 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.
  • 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!

Downloads

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

Yay, we are back!

After 3.0 came out, we spent some time in bugfix-mode, then we had a 20% week, 2 devspeed weeks, and the last week was mainly spent planning the next release. So that's why there has not been much visible progress recently lately. Development on core 3.1 features has started, but in this milestone we mainly ship all the bugfixes we did for 3.0.1, some small improvements, and three 20% projects.

New Webstart Installer

We are trying something new. While we will provide the downloadable files too, we encourage you to try our webstart based evaluation installer. Visit http://webstart.atlassian.com/confluence-3.1-m1-r2/confluence.jnlp for a snappy installation experience.

New Native Mac Installer

When you go to the download section, you will notice a new DMG file. This contains our new native experimental Mac installer. Give it a try and tell us what you think. Instructions coming soon!

And here are all the cool features in M1 you will get.

Interactive "Get more"

Recently updated macros are now interactive. You will get a little "More" link to load new updates dynamically within the page. This small but awesome feature can also be found on your network page, and in the space's recent update tab. It doesn't screenshot too well, so try it out for yourself. Anyway here is what the macro looks like:

And here is what the network tab looks like:

Caveats:

  • We feel that the link is a bit small and can be mistaken for a normal link. Especially on the static pages (network, updates in space) it makes sense to make the button much larger and more prominent. We will work with Design to find a solution
  • The link also needs to go into the profile page (so you can see more updates on everyone's stream), and into the status tab. Dave will add that soon

This is a Dave Loeng 20% production

Draft diffs and visibility

Always wondered what your old drafts were about? Or when a draft is being saved, what part of that huge document you're editing has actually changed? Well, now you can, thanks to DraftDiffs.

View the diff right from the edit page:

View what your old drafts are about from the drafts overview page:

Which takes you to this screen:

Known issues: Annoying Javascript alert when there are no changes at all.This feature unfortunately also highlights our roundtripping bugs... ahem...

This is a Brian Nguyen 20% production

Small Improvements

Edit loss warning

Whenever you are in edit mode and decide to leave the page or close it, you will now get a warning popup. This is especially useful when writing comments (no drafts...) and for technically challenged people who don't understand drafts in the first place. As raised in the JIRA issue, we may have to provide a setting to disable these warnings (it can be a bit annoying if you like to change your mind often), so watch CONF-16075 for updates. The idea has been raised that we may only want this feature for comments when no drafts are being saved. We will dogfood this over the next few weeks, and see how we like it or not.

Gradient

This is just an experiment, probably not shipping as a default for 3.1, but worth a look. Do you like it?

More options to search for by time

We added two more options to filter by time: Last 6 months, Last year, Last 2 years, and fixed the calculation for today/yesterday by making it work by 24h instead of what the server thinks is midnight. 48h obviously encompasses the last 24 hours two, which was akward in the old system, where yesterday would really just mean yesterday, but not today.

Plugin points in the editor

We were approached by a developer who wants to write a spellchecker plugin for Confluence, so Agnes volunteered to pluginpointinize the editor. You won't see anything right now, but it will make many plugin authors happy. Read the documentation for how to write plugins for the editor.

This is an Agnes Ro 20% production

"Link to this page" Dialog

In order to make Tiny Links more accessible, we added a new Menu option which opens a new dialog, which shows the three ways to link to a page. Full URL, TinyURL, and Wiki Link. Probably the Full URL is not as important, but the dialog looked a bit unbalanced, and it makes it clearer that both URL's are equivalent.

Selecting the menu opens up this dialog, with the Tiny Link conveniently selected.

We didn't rename Tiny Links to Permalinks, as has been suggested. What do you think, should we?

This is the final Chris Broadfoot 20% production.

  • No labels

7 Comments

  1. Some nice improvements here. Especially the diff on drafts and preventing accidental comment losses.

  2. Anonymous

    I like permalink.  It make it more clear to a user why they should use that. Tinyurl just make it seem its for convenience.

    1. Anonymous

      I agree Permalink is better.  It actually describes better to the user, why the link is there.

  3. Anonymous

    "permalink" does two things:

    1.  communicates programming intent to keep these links stable.

    2.  requires no special training, new employees actually understand what they are, and quickly grasp the difference between that link and a link which is based on an editable title.   

    my vote would be to make them really permanent and call them permalinks.

    michael b.

  4. I was hoping to see some front-end performance optimizations in this release (see http://jira.atlassian.com/browse/CONF-16082), is that still going to happen for Confluence 3.1?

    1. Hi Jason,

      I hope that you find our developers' comments in the improvement request useful.

      Cheers,
      Azwandi

  5. Anonymous

    One other thing that would be worth looking at is journaling and backups. If we loose an hour of confluence work at this point, it's a tragedy. Backup support for large databases would be very very helpful.