In the spirit of openness, we wanted to share our plans around upcoming breaking changes across many Server Products. We’re open about our plans so the Atlassian Ecosystem can plan ahead to ensure a smooth experience for our customers. We’ve consolidated these updates into a single, easy to digest, post and plan to provide monthly updates from now until the end of the year.
The AUI team is currently re-architecting and breaking up the AUI front-end library in to smaller pieces. The team’s aim is to allow developers to use only what they need from AUI, so that they can improve their product’s and plugin’s runtime performance.
The code shipped in AUI’s default web-resources and batch files will change. Some deprecated utility methods in AUI will be removed. Individual HTML markup patterns and component APIs will not change.
The AUI team posted their direction for AUI 8 in the developer community. The community post dives deeper in to the planned changes and outlines an upgrade path.
The AUI team is tracking to ship this release via NPM in early- to mid-August. Atlassian Server products will ship the library update in their upcoming major versions.
Found a bug? Raise a ticket in the AUI project on our Ecosystem Jira.
We’re planning to ship Bitbucket Server 6.0 late November, 2018. We have some exciting new features lined up for the release. For one of these features it is necessary for us to deprecate direct access to repositories on disk for apps. You can find the necessary details in the API changelog. Apart from this, we plan to add support for Java 11. Java 8 is reaching end of life in January 2019. After this time no further fixes, including security patches will be available for it. As a core dependency for Bitbucket Server such patches are critical.
In Confluence 6.10 we shipped read-only mode for Confluence Data Center. Read-Only Mode for Data Center customers helps admins perform routine maintenance, recover from unexpected problems, or prepare to migrate content to a new site. It is important that you check that your app is compatible, and to mark it compatible to help inform system administrators, Check out how to make your add-on compatible with read-only mode for all the details.
In 6.10, we also introduced a new way to handle resource intensive tasks in a sandbox, starting with document conversions. The sandboxes aren’t available for add-ons at present, but this is something we might consider doing in the future. Check out preparing for Confluence 6.11 for more details.
We are currently planning to release support for Java 11 in an upcoming feature release, circa October 2018. This will allow the use of the JDK 11, however without support to use any new features or functionality at this time.
We are also continuing our work on the TinyMCE editor upgrade from 3.x to 4.x. This has been ongoing for some time now, and hopefully everyone has checked their apps for compatibility. If not, check out how to test your add on with the upgraded TinyMCE4 editor.
Our customers are moving to IPv6 and Atlassian Server products are now compatible in these new environments. We’ve recently shipped IPv6 support for Bitbucket Server(v5.8), Confluence Server (v6.9), Jira Service Desk Server (v3.14), Jira Server (v7.11). Portfolio for Jira Server version 2.15 is compatible with Jira Server 7.11 and is therefore IPv6 compliant. We are working on making Bamboo IPv6 compliant and will be shipping that in this quarter. We plan to make FeCru compliant in 2019 and have no plans to add support for Hipchat Data Center.
There is more information and implementation advice available in the product release notes.
Jira Software Server
We’re planning to ship Jira Software 8.0 in October 2018. We’re still refining the scope of the release but our current aim is for it to include improvements to the search sub-system via an upgrade of Lucene, front-end improvements such as jQuery and Skate library updates and deprecation of global variables in favor of AMD modules (for more details, see this post), Agile and Kanban boards performance improvements, and an upgrade to use new platform components and libraries which are compatible with Java 11.
The JSD team plans to ship Jira Service Desk 4.0 release, in step with Jira Software 8.0 in late October 2018. As a major release update it’s important for our customers to be informed so they can absorb the changes and benefit from it. Jira Service Desk is built on the Jira platform, it stands to benefit from and incorporate changes being brought in by Jira. In particular JSD will incorporate sub-system improvements related to Lucene. There would also be updates to the Fugue code.
We’re in the process of upgrading our Server products to support Java 11. As mentioned above this is in progress for Jira Software, Bitbucket Server and Confluence Server. Bamboo, FeCru, Portfolio for Jira and Jira Service Desk and Crowd have yet to roadmap this work but it is our intention that all maintained Server products will provide support for Java 11. We are also considering supporting OpenJDK for Java 8 and 11, please share with us your feedback and if you would like us to support it.
If you have any questions or concerns about any of the changes mentioned here please raise a ticket in the Ecosystem Developer Service Desk.