Confluence Docs 3.0 : Release Notes 3.0-m6 ("Milestone 6") This page last changed on Mar 16, 2009 by pfragemann. 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. # Summary This milestone is mainly about polishing features that were introduced previously, and a bit of back-end work for security and performance. We have fixed plenty of bugs of M5 too, and will keep fixing for M7. # Known issues Given the recent work that has been done to improve "recent updates" (CONF-14434), updates shown on the dashboard will be affected shortly after the upgrade. You may notice that only changes made _after_ the upgrade will show. This will be rectified as soon as the index is rebuilt. # Improvements and new Features ### New PDF Export This milestone contains the first cut of the Improved PDF export, which also give you more control over the conversion process by allowing you to use CSS. Please find the detailed documentaton on CAC. CONF-2079 There are still plenty of known bugs with the new PDF, we included it a bit early to be able to get feedback on the CSS-styling process, not for beta-testing purposes... ### Engine Room The ER team has implemented several more important fixes and improvements in this milestone: supportability - integrated thread-dump tool in the administration screen (CONF-12395) security - editing comments in wiki markup is no longer double-HTML-escaped in anti-XSS mode (CONF-14601) cluster performance - avoid unnecessary updates to distributed cache to improve cluster performance (CONF-14657) general performance - improve performance of retrieving many attachments, like on the attachments page (CONF-14422) front-end performance - add caching headers to attachments rendered with a "?version=x" parameter (CONF-8034). ### Office Connector When launching an external editor from Confluence, you don't have to login again. CONF-14705 You can now monitor what is in the conversion queue and what is actually being converted CONF-14707 ### Macro Browser The following bugs have been fixed: Errors were reported by the JIRA trusted connection. APP_UNKNOWN; Unknown Application: {0}; ["confluence:4557196"]
JIRA Issues (0 issues)
Type | Key | Summary | Assignee | Reporter | Priority | Status | Resolution | Created | Updated | Due
--- | --- | --- | --- | --- | --- | --- | --- | --- | --- | ---
### Status and Follow The following bugs have been fixed: Errors were reported by the JIRA trusted connection. APP_UNKNOWN; Unknown Application: {0}; ["confluence:4557196"]
JIRA Issues (0 issues)
Type | Key | Summary | Assignee | Reporter | Priority | Status | Resolution | Created | Updated | Due
--- | --- | --- | --- | --- | --- | --- | --- | --- | --- | ---
### Bugfix-team It's safe to use Sections and Columns in the RTE again. (CONF-13823, CONF-14282)

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