July 1 the support period for Mercurial repositories on the Bitbucket collaborative development platform. The cessation of Mercurial support in favor of Git was announced in August last year, after which the creation of new Mercurial repositories was prohibited on February 1, 2020. The final phase of the deprecation of Mercurial is scheduled for July 1, 2020, which will involve disabling all Mercurial-related functionality in Bitbucket, including shutting down Mercurial-specific APIs and deleting all Mercurial repositories.
Users are advised to migrate to Git by using or switch to open-source hosting. For instance, Mercurial is supported on , , and .
Interestingly, the Bitbucket service was initially focused solely on Mercurial, but starting in 2011, it began to also support for Git. Recently, Bitbucket has focused on developing a service for managing the full software development lifecycle, and supporting two version control systems hinders and complicates the implementation of their plans. Git has been chosen as a more relevant, functional, and in-demand product.
Additionally, it is worth noting Bitbucket will cease to use the term "master" by default for main branches, as this term has recently been considered politically incorrect, evokes slavery, and is perceived as offensive by some community members. Developers will be offered the opportunity to choose their own name for the main branch, such as "Main." Previously, similar intentions were put forward by and .
The Git project will also make a change to allow developers to choose their own name for the first branch when creating a new repository. When executing the command "git init," a branch named "master" is created by default. The first step will be to add a setting to change the name of the main branch for newly created repositories. The default behavior of Git will remain for now, and the question of changing the default name is still under discussion, with no decision on this matter yet made.
Source: opennet.ru
