Bitbucket Server 5.11 release notes
2018 年 5 月 29 日
If you are upgrading from an earlier version, refer to the Bitbucket Server upgrade guide.
The Bitbucket 5.11 changelog is at the bottom of this page.
コミット ページでのプル リクエストへのリンク
There's always a reason behind a code change, but sometimes it's hard to figure out what that reason was. When working with code in your IDE (Integrated Development Environment), you can often locate the commit which introduced a line of code, but the commit doesn't always tell the full story. Most conversations and discussions will happen on a pull request, where the full scope of the change is apparent. Previously in Bitbucket, it was difficult to work out which pull requests a commit related to. In this release, we've introduced pull request links on each commit, so you can jump straight to the pull request to get the full story, and understand exactly what's happening. For a summary of the benefits of pull request watch this short video.
JIT (Just-In-Time) fetching
A clone or fetch from a smart mirror may be outdated if the smart mirror is not in sync with the primary cluster, possibly due to restart or sync that's in progress. With this improvement, when a client attempts to clone or fetch a repository from a smart mirror, and the smart mirror 'knows' that its local copy is stale, the smart mirror will attempt to synchronize the repository with the upstream just before servicing the clone or fetch request.
This section will contain information about the Bitbucket Server 5.11 minor releases as they become available. These releases will be free to all customers with active Bitbucket Server software maintenance.
If you are upgrading from an earlier version of Bitbucket Server, check the Bitbucket Server upgrade guide.
The issues listed below are the highlights of all those that have been resolved for the Bitbucket Server 5.11.x releases, and are ordered by votes received.
Bitbucket Server 5.11.0 was an internal release and is not available for download.