Meelogic Atlassian Blog

Bitbucket 6.10 release notes

✓ How is an Enterprise release different from other release types?

✓ Be better prepared when you upgrade to Bitbucket Server 7.0

✓ Unsupported operating systems

✓ 2-way diff for pull requests

✓ End of support announcements

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 at the beginning of next year, you may notice some changes, possibly lower memory consumption. The only catch is that Bitbucket Server will no longer run on unsupported operating systems, as deploying this improvement required a switch from using Java 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 are not on a supported platform, it will display a warning banner and warning in the user interface.

2-way diff for pull requests

Bitbucket 7.0 changes from a 3-way diff to a 2-way diff This means that starting in 7.0, when a pull request is displayed, the displayed diff is a diff between the tip of the source branch and its common predecessor with the target branch. As a result you will 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

    As a result, Redhat Enterprise Linux 5 and earlier will not be supported.