Confluence 3.5 : Confluence 3.5-m4 ("Milestone 4") Release Notes
This page last changed on Jan 12, 2011 by mryall.
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?
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 ProcedureFollow 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! DownloadsAll development releases are available from the development releases page on the Atlassian website. Previous Milestone(s)FeaturesNotification ImprovementsWe have continued work further notification improvements in this milestone. Notifications about changes are now sent with From address of the email including the name of the user who made the change. This behaves the same as in JIRA and should make it a lot easier to decipher Confluence notifications in your inbox. The format of the From address used in emails can be customised by Confluence administrators under the Mail Servers configuration, using the same formats as in JIRA. The default format is “<user’s full name> (Confluence)”. Automatic Language DetectionThis milestone includes the ability to select a user's preferred language automatically, by respecting the Accept-Language header which the user's browser sends. Unless a language preference has been made in the profile settings, the closest matching language to the one suggested by the browser will be used. New Space DirectoryOne of the biggest problems facing customers with large installations of Confluence is the scalability of the dashboard. It's a well-known problem that the list of spaces on the dashboard doesn't scale for sites with more than a few dozen spaces. We've added a new screen called the Space Directory where you can browse every space without having to use the Dashboard.
The Space Directory will eventually make the 'All' list of spaces on the dashboard obsolete, and make the performance of the dashboard much better for our large customers. Multimedia AutocompleteWe have also continued work on editor improvements for Confluence 3.5. In this milestone, you can now embed multimedia files into your page via autocomplete. Try it out by hitting “!” in the editor and entering the name of a movie file attached in Confluence. Remote API for Watching and Managing WatchersWe've added a bunch of new methods into the Confluence SOAP and XML-RPC APIs for watching and managing watchers. The new methods in the remote API mimic the watch functionality exposed through the UI:
There's also a very obscure old method called getBlogEntryByDayAndTitle which only allowed you to look up a blog post in the current month. We've added a new method to look up any blog post by date and title:
Small improvements
Bug fixesMultimedia Macro bug fixes
User management bug fixes
Other bug fixes
Improvements for developers
Known issues
Note about CONFDEV issuesThe Confluence team is using an internal JIRA project for tracking development with GreenHopper. The CONFDEV issues refer to our internal tracking numbers for user stories or bugs discovered and fixed within the scope of a release. ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
![]() |
Document generated by Confluence on Mar 16, 2011 18:45 |