Confluence Docs 3.0 : Release Notes 3.0-m5 ("Milestone 5") This page last changed on Mar 09, 2009 by ggaskell. 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.1, which will be probably shipped in Q4/2009. 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.
Our milestone releases aim 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, which are scheduled to be fixed in the next milestone, or completely new bugs unknown even to us. Additionally, our performance-testing and compatibility testing for databases and application servers is not done to the full extent. So, for example, a milestone release might 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.0.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 Development Releases on the Atlassian website. # Issues resolved or improved in this milestone since Milestone 3 ### Macro Browser (in Markup Editor) The Macro Browser is now available in the wiki markup editor! Features are listed below.
##### Browse Macros You can now browse through a list of categorised macros and select a macro to insert. Macros that do not have categories define can be found in the 'All' categories tab. To insert a macro, you can either double click on the macro or click it once and then click the 'Next' button. ##### Insert Macro For macros that have parameter metadata defined, you will see parameter labels and descriptions with the appropriate input fields. So far we are handling boolean and select-one-from-list type parameters. Everything else is considered a string. Please note that there is no field validation. For macros that don't have the parameter metadata defined, you will see a single input field for the macro parameters and its notation guide help (if any) below. ##### Preview Macro A default preview will be loaded only if the macro doesn't have required parameters. The preview can be updated by clicking on the 'Preview' button. This button location will change in the future. ##### Edit Macro You can also edit a macro by placing your cursor in the start tag of a macro and then clicking the Macro Browser icon. It should display the 'Insert X Macro' page with it's parameters populated. ##### Known Issues
Macro summary and parameter descriptions are currently under review by the tech writing team, so please ignore grammar/spelling/crappy English for this milestone. The macro icons (displayed in browse macros) are temporary. Hopefully we will be able to get much sexier icons. Some macros falsely declare they have bodies (e.g. gallery) so you may see some unnecessary body text areas
### Community Several major community features have their debut in this milestone. ##### Status This milestone, we are releasing the first version of the Status feature. There is still a lot of work to be done, it's not particularly polished but we want your feedback.
First of all, set your status from the user menu, where you'll get a dialog box allowing you to enter your new status. You can see your status and others' statuses from user hover, under the "Status List" option in user profiles, the "Favourite People" tab (see below), personal space sidebar (see below). ##### Follow Marking another user as "favourite" is now meaningful. In milestone 5, you'll be able to get a list of statuses from the people you follow.
Check out the "Favourite People" tab in your user profile – you can get there via your user menu. It will show you who you're following, and who's following you. You can also quickly follow someone with the user search, and see a list of status updates from the people you follow. ##### Personal Space Sidebar With this release, we now have some structured form of a user profile for every user. On the right of any personal space*, there'll be a sidebar with various details of the person's space you're viewing. Don't worry, you can easily collapse the sidebar and it'll shift out of sight. Once you collapse the sidebar, it will stay collapsed for all personal spaces for the duration of your login session. Here's what it looks like:
We plan to put more information on the sidebar, at the moment it looks a little silly if the user doesn't have a status set and hasn't filled out any of the extra profile fields we added last milestone. This only works in the Default Theme. ##### Known Issues
There are a few known issues with the Community work, the biggest thing is what you see at the moment is a first cut of the functionality, we plan to "sexy" it up a bit and make the status and profile pages look a lot nicer. You will also notice that when you favourite another user you will need to wait for the index to be flushed for your changes to be applied. This will be improved in a future milestone.
### Bugfixes There are two relevant bug fixes in this milestone: Configuration to prevent anonymous users accessing user profile information (CONF-13276) Cannot insert links with Unicode characters in the URL (CONF-12707). ### Engine Room The Engine Room team has delivered one more performance improvement and a significant security improvement this milestone: Attachment retrieval should cache attachment IDs (CONF-14422) Anti-XSS mode is now enabled by default (CONF-12573). We also fixed the regression in the previous milestone (M4) where pages with thousands of attachment versions brought all attachment retrievals to a grinding halt. Attachments: BrowseMacros.png (image/png) EditorToolbar.png (image/png) InsertMacro.png (image/png) InsertMacroFreeform.png (image/png) m6-favourite-list.png (image/png) m6-personal-sidebar.png (image/png) m6-quick-follow.png (image/png) m6-status-dialog.png (image/png) m6-status-menu.png (image/png)

Document generated by Confluence on Nov 05, 2009 23:27