Confluence Docs 3.0 : Release Notes 3.0-m4 ("Milestone 4")
This page last changed on Feb 05, 2009 by don.willis@atlassian.com.
Milestone release advisory
For all production use and testing of Confluence, please use the latest official release. Who should upgrade?
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 ProcedureFollow 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! DownloadsAll development releases are available from Development Releases on the Atlassian website. Issues resolved or improved in this milestone since Confluence 3.0 Milestone 3Experimental Macro BrowserThe Macro Browser is now available in the wiki markup editor, however it is currently not in a state for proper use. It is quite buggy and has been included for QA and the dev team, so please do not raise any issues against it yet. CommunityUser Hover FixesA lot of outstanding issues with User Hover were fixed for m4. First Cut of User ProfilesThe profile tabs have been rearranged into a more intuitive order, with general and email preferences moved to a separate "Settings" tab:
Performance ImprovementsWe did the following small performance improvements:
Although the performance improvement hasn't been as dramatically as in M2, but we still see a solid trend towards shorter and less varying response times. The overall performance improvement is around 10%-15% with more to come in the next milestones. Known issues
Check out JIRA for the full list of known bugs ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
![]() |
Document generated by Confluence on Nov 05, 2009 23:27 |