Join the community to find out what other Atlassian users are discussing, debating and creating.
Hi Atlassian community,
Amber Van Hecke from the Bitbucket Product team here.
The Bitbucket team recently announced that we will be removing Mercurial support from Bitbucket Cloud and the API. Mercurial features and repositories will be officially removed from Bitbucket and its API on June 1, 2020.
Why we’re doubling focus on Git
It wasn’t an easy decision, and Mercurial will always have a special place in Bitbucket's history.
Bitbucket has steadily grown beyond being just a platform for version control to being a place to manage the entire software development lifecycle. In answer to customer need and market trends, this year we will focus on building deeper integrations to enhance automation and collaboration. Our improvements will make it even easier and safer to plan, code, test, and deploy all from within Bitbucket.
Building quality features requires intense focus, and supporting two version control systems means splitting focus - doubling shipping time and technical overhead. With Git being the more popularly used tool, Mercurial runs the risk of overlooked issues as we scale.
According 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. In fact, Mercurial usage on Bitbucket is steadily declining, and the percentage of new Bitbucket users choosing Mercurial has fallen to less than 1%. This deprecation will allow us to singularly focus on building the best possible experience for the lions share of the market and our users.
Let’s chat migration & exporting
Our hope is for affected teams to be able to stay in Bitbucket. That’s why we created this forum to discuss conversion tools, best practices, and help troubleshoot any issues you might come across.
We also realize that others may want to continue using Mercurial on a different hosting service. We’re here to help you discover the best export options in that case as well.
There is no one-size-fits-all solution as the best alternative will depend on your team’s unique use case. Looking forward to helping make this transition as seamless as possible.
avh
Atlassian TeamProduct Manager, Bitbucket
2 accepted answers
Hey Community! I work on the Bitbucket product marketing team. With Halloween approaching, we wanted to discuss a topic tailor-made for October: development horror stories. Whether it was a lurk...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
272 comments