This deprecation will enable us to focus on building the best possible experience for our users. In fact, Mercurial usage on Bitbucket is steadily declining, and the percentage of new Bitbucket users choosing Mercurial has fallen to less than 1%. With Git being the more popularly used tool, Mercurial runs the risk of overlooked issues as we scale.Īccording to a Stack Overflow Developer Survey, almost 90% of developers use Git, while Mercurial is the least popular version control system with only about 3% developer adoption. Our improvements will make it even easier and safer to plan, code, test, and deploy all from within Bitbucket.īuilding quality features requires intense focus, and supporting two version control systems means splitting focus – doubling shipping time and technical overhead. This year we will concentrate on building deeper integrations to enhance automation and collaboration.
#Bitbucket push with tortoisehg software#
In this time, Bitbucket has steadily grown from being just a version control management tool to being a place to manage the entire software development lifecycle. DevOps adoption has skyrocketed over the last decade and our customers are adopting this new way of working at an exponential rate. This wasn’t an easy decision, and Mercurial will always have a special place in Bitbucket’s history. All hg repos, wikis, and snippets will be in read-only mode. July 1, 2020: users will not be able to use Mercurial features.February 1, 2020: users will no longer be able to create new Mercurial repositories.Here are the key dates as we sunset Mercurial functionality: The timeline and how this may affect your team Read on to learn more about this decision, the important timelines, and get migration resources and support. Mercurial features and repositories will be officially deprecated on July 1, 2020.
As we surpass 10 million registered users on the platform, we're at a point in our growth where we are conducting a deeper evaluation of the market and how we can best support our users going forward.Īfter much consideration, we've decided to remove Mercurial support from Bitbucket Cloud and its API. When we launched, centralized version control was the norm and we only supported Mercurial repos.īut Git adoption has grown over the years to become the default system, helping teams of all sizes work faster as they become more distributed. The version control software market has evolved a lot since Bitbucket began in 2008. After July 8th, 2020 they will no longer be accessible. Today, mercurial repositories, snippets, and wikis will turn to read-only mode. All hg repos have now been disabled and cannot be accessed.
0 kommentar(er)
