You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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 July 1, 2020. (Note: We have extended 30 days from the original date of 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.