Confluence 1.3-DR3 is the third development release in the cycle leading up to Confluence 1.3 - and a momentous day in the history of Confluence.
We've finally made it to that special point in every applications life.
Confluence has evolved.
1.3-DR3 is best summed up by Jamie Zawinski's Law of Software Envelopment:
Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can.
That's right - Confluence now has more content than ever before. It reads, stores and indexes email. Oh, and as a nifty little bonus - it also indexes Word documents, PDF documents, RTF documents, Excel spreadsheets, PowerPoint files, text files, source files etc... attached to your mail!
Have we got your interest? How does all this magic happen you ask? Read on to pull back the curtain.
Who should upgrade?
Development releases are snapshots of the ongoing Confluence development process. We make them available for customers who are willing to risk an unpolished release in order to have early access to new features.
If you want to be running the most stable and most reliable version of Confluence, you should stick with the official, numbered releases.
Upgrading Confluence should be pretty easy. If you are upgrading from Confluence 1.2 or higher, you can find instructions here. We strongly recommend that you backup your
confluence.home directory and database before upgrading!
If you are upgrading from Confluence 1.1.2 or earlier, be sure to read the upgrade instructions in the Confluence 1.2 release notes.
Note: Because we have made significant changes to permissions in 1.3-DR2, you should check that your user permissions have been correctly migrated. The upgrade manager should ensure permissions remain consistent between versions, but as with anything related to security, it's best to double-check.
New Features in Confluence 1.3-DR2
Confluence is a collaboration tool. When communication happens through email instead of through Confluence, information will get lost in the depths of someone's mail folders, instead of shared with the team, archived, interlinked and indexed.
While we would love to see all collaboration within a group to happen through Confluence, it's often not possible to change the way people work. So instead of finding new ways to force people to use Confluence instead of email, why not route all the relevant email into Confluence?
It is now possible to archive email within a Confluence space. The support for mail is only just getting started in DR3, but we believe this is an incredibly useful direction for Confluence to go, and will be expanding and improving the mail integration in future releases.
Confluence spaces can retrieve mail periodically from a POP mailbox (this will delete all mail from that POP account, so don't try it on an account you want to keep mail on), or space administrators can import mail directly from a standard mbox-format mail file.
Once mail is imported into Confluence, it can be browsed chronologically from the Content pane of the Space Summary page, and can be searched through Confluence's search interface.
In the future, we will be adding new ways to link to and between email (bringing the email closer to the other content of the wiki), proper representation of email threads, more flexible search, and much, much more.
Read the Mail Archiving FAQ for more information
Want to play with it now?
We love to play with features right now, so here's how you can:
- Testing mail search is a snap.
- Testing mailing content into Confluence is also easy. It will also be indexed.
Improved Indexing Performance
We now make much more efficient use of resources by batching updates to full-text search index. This should lead to improved performance for many tasks within Confluence, but will mean that it may take up to a minute for a change in the site to be reflected in the site's index. (CONF-2029
Many of the librares Confluence is dependent on have been upgraded for this release, which should result in improved stability and performance.
Bugs fixed for 1.3-DR3
We've fixed a handful of issues specifically for 1.3-DR3, take a look in JIRA for the full list.