Confluence Docs 3.3 : Release Notes 3.0-m7 ("Milestone 7")
This page last changed on Mar 31, 2009 by pfragemann.
Milestone release advisory
For all production use and testing of Confluence, please use the latest official release. 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 (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 ProcedureFollow 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! DownloadsAll development releases are available from the development releases page on the Atlassian website. SummaryThe Confluence team is proud to present another incremental milestone, called M7. We are currently aiming at shipping M8 in two weeks and M9 in four weeks. M9 will be almost feature-complete and therefore similar to a beta release. After a couple of betas and release candidates we intend to ship Confluence 3 in late May. As always, things can still change a little, so there is no fixed date. But if you are a plugin developer, you want to have your plugin tested well before the big marketing buzz kicks in. We try to remain as backward-compatible as we can for Confluence 3, but if something slipped through the cracks we need your feedback, and we need it now. So do have a look at this milestone release and tell us what you think. Macro Browser and Rich Text EditorYou can now choose the kind of right-click context menu you want in the Rich Text Editor. A new button on the toolbar, handily called "Toggle context menu", toggles between the browser's default context menu and our TinyMCE one. You can also tell the TinyMCE context menu that it isn't wanted via the "Disable context menu" option.
The filtering logic has been added to AUI as a new commented method of AJS, "filterBySearch" - feel free to use it.
Community ImprovementsThis milestone shows a number of improvements from the Community Team. Profile LayoutIn the spirit of making the profile page actually page you want to visit, it's been given a facelift and has now come closer in line with out stardard UI. It also includes your current status is clearly visible at the top of the profile page. For now you have a Status Updates section on the right hand side of the profile page, the next milestone will see this will be replaced with the new Recently Updated Macro (see below) so it will include other kinds of activity as well. It's here now because otherwise you wouldn't have anywhere to delete or clear your status, eventually will be moved to another tab and/or page.
User Status Updates
Recently Updated MacroThis is the first milestone that shows the hard work that David Loeng and Chris Broadfoot have been doing with our Recently Updated Macro. To build up activity in the old recently updated macro the process would simply query the lastModified date of all the relevant content, then sort it accordingly. The side effect of this was, if two people edited the same page, you would only see the one edit in your list. Not only that, if you wanted to follow a certain user's activity and someone edited a page after them, you wouldn't see any update! We've worked very hard on this and changed the way Confluence stores changes to documents and now tracks all changes every time a document, page, profile, status, anything, is updated. This screen shot shows two edits from two different people on the same document, something that wasn't previously possible. These changes were critical for implementing a proper follow feature for 3.0.
Bug FixesA number of bugs have been fixed by the community team, here are a list of some of the main ones:
Plus a number of other fixes. PDF export teamRemoved the PDF Export++ option. The new PDF export is what you get when you select just PDF Export. The old PDF export was removed.
Bugs fixedCONF-14906 - Fonts are too large in the page index macro when exported to PDF ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
![]() |
Document generated by Confluence on Jul 09, 2010 01:11 |