July 1 support time for Mercurial repositories in the Bitbucket collaborative development platform. The end of support for Mercurial in favor of Git was in August last year, after which, on February 1, 2020, the creation of new Mercurial repositories was prohibited. July 1, 2020 marks the final phase of the Mercurial phase-out, which means disabling all Mercurial-related functionality in Bitbucket, including discontinuing Mercurial-specific APIs and deleting all Mercurial repositories.
Users are encouraged to migrate to Git using to convert repositories, or go to open source hosting. For example, Mercurial support is provided in , , ΠΈ .
It is noteworthy that initially the Bitbucket service focused only on Mercurial, but since 2011 it has also become Git support. Lately, Bitbucket has been focusing on the development of a service for managing the full software development cycle, and the support of two version control systems slows down and complicates the implementation of the plans. Git was chosen as a more relevant, functional and popular product.
In addition, it can be noted Bitbucket will no longer use the default word "master" for master branches, as the word has recently been considered politically incorrect, reminiscent of slavery, and perceived as offensive to some community members. Developers will be given the option to choose their own naming convention for the master branch, such as "Main". Platforms have previously expressed this intention ΠΈ .
Git project also make a change to allow the developer to choose the name for the first branch when creating a new repository. When executing the "git init" command, the "master" branch is created by default. The first step is to add a setting to change the upstream name for the repositories you create. Git's default behavior is still in place and the issue of changing the default name is still under discussion, no decision has been made in this area.
Source: opennet.ru