News from Atlassian:
Confluence 6.1 is out! So what’s in it?
AWS Quick Starts: Confluence Data Center joins the AWS Quick Starts family. Now customers can deploy their Confluence Data Center cluster in just a few minutes, including load balancer, database and all the connectivity needed. While we’ve made it super easy to get up and running with Confluence Data Center in AWS, if customers are not quite ready to upgrade, they can still use AWS to host Confluence Server.
SAML 2.0: Delivering on our Summit commitment, we now have SAML 2.0 single sign-on support for Confluence Data Center. With SAML 2.0 admins can integrate Confluence Data Center into their existing infrastructure to give their teams a simple and secure way to sign in.
Team Playbook: Working as a team is really hard, and tools alone won’t fix that. At Atlassian we developed a playbook that changed the way our teams work. Confluence Team Playbook Blueprints give users a way to create new pages based on pre-defined content for some Team Playbook ‘plays’. Users view the blueprints through the ‘Create’ dialog which offers a description of the play. Kick off with a Health Monitor workshop to get a reading on your vital signs, or just dive straight into the plays.
Improved Collaborative Editing: Since the the release of collaborative editing in Confluence 6.0, we’ve seen a lot of teams working together and getting on the same page. We’ve now now made it even easier to get started. Customers no longer need to make changes to your reverse proxy configuration to use the internal Synchrony proxy. It just works, right out of the box. Automated fallback to XHR means that if a user cannot connect to Confluence via WebSockets, they can still edit pages, hassle free. If your customer upgraded to Confluence 6.0 but had to turn collaborative editing off because of infrastructure or environmental problems, we’d ask you to encourage them to give it another try.