Bitbucket Server 6.10 release notes
14 January 2020
We’re excited to announce that the Bitbucket Server 6.10 release is now available.
Bitbucket Server 6.10
is an Enterprise release
This means we'll provide bug fix releases until 6.10 reaches end of life to address critical security, stability, data integrity, and performance issues.
How is an Enterprise release different from other release types?
An Enterprise release for Bitbucket Server, like other releases, receives updates in the form of bug fix releases and is supported for two years. The main difference is that an Enterprise release gets bug fix releases throughout its two-year support window.
Bitbucket Server has multiple feature releases within the same year. Older feature releases no longer receive bug fix releases, as we focus on updating the latest feature release.
Enterprise releases help address this with the assurance of fixes for critical bugs and security issues regardless of whether a newer feature release is already available. This gives you the option to stay on an Enterprise release throughout its two-year support window.
Be better prepared when you upgrade to Bitbucket Server 7.0
Unsupported operating systems
After upgrading to 7.0 early next year, you may notice reduced memory consumption due to some changes we’re making. The only catch is that Bitbucket Server will no longer run on unsupported operating systems because delivering that improvement required switching from using Java’s
ProcessBuilder to manage
git processes, to a different approach based on native operating system APIs.
The 7.0 release isn’t changing what platforms are supported, rather it’s simply enforcing the supported platforms we’ve always had. To make sure you have ample time to prepare, we put a check in place that detects whether or not you’re on a supported platform. If the system detects that you aren’t, we’ll display a warning banner and an alert in the UI.
More details to help you determine what is supported can be found in our Supported platforms page.
2-way diff for pull requests
We’re switching from a 3-way diff to a 2-way diff in Bitbucket 7.0. This means that from 7.0 onward, when viewing a pull request, the diff shown is a diff between the tip of the source branch and its common ancestor with the target branch. As a result of this switch, you’ll see the following primary changes:
Pull requests will no longer visualize conflicts. The UI will still indicate when a pull request has conflicts, but they will no longer be marked up in the diff.
Equivalent changes will not be “hidden”. If two different commits make the same change, a 3-way diff shows nothing (since it’s done the merge and knows nothing has changed), but a 2-way diff will still show the change.
Lower CPU load. The processing required for a 2-way diff is substantially less than the requirements for a 3-way diff.
End of support announcements
- Internet Explorer 11 – as previously announced, support for Internet Explorer 11 will be removed in Bitbucket Server 7.0.
- MariaDB 10.0.0 has been deprecated, and support will be removed in Bitbucket Server 7.0.
- Redhat Enterprise Linux 5 and earlier – in Bitbucket Server 7.0, support will be removed for:
- kernel version older than 2.6.17
- glibc version older than 2.7
Get ready to upgrade
Upgrading from an older version? Check out the Bitbucket Server 6.10 Enterprise Release Change Log for a collection of all the changes between Bitbucket Server 6.0 and 6.10.
Released 31 March 2020
Released 10 March 2020
Released 9 February 2020
Released 14 January 2020