[Openid-specs-mobile-profile] Sunsetting Mercurial support in Bitbucket
joseph.heenan at fintechlabs.io
Wed Aug 21 10:34:52 UTC 2019
I’m currently keeping an eye on this.
I don’t think I reported back to the group, but my previous investigation on hg -> git conversion on bitbucket suggested it was essentially impossible to migrate to git and keep issues and pull requests intact.
That’s still the case even after this announcement, which is disappointing. Atlassian’s current statement appears to be that they will be deleting all mercurial projects in 2020 we are likely to lose access to the issues and pull requests regardless, and Atlassian are not providing any migration path to git.
I suggest waiting for the dust to settle and reviewing again in a month or so.
Are there any other OIDF groups that are still using mercurial?
> On 21 Aug 2019, at 07:56, Dave Tonge <dave.tonge at momentumft.co.uk> wrote:
> Looks like moving to git will be necessary.
> ---------- Forwarded message ---------
> From: Atlassian <noreply at mailer.atlassian.com <mailto:noreply at mailer.atlassian.com>>
> Date: Tue, Aug 20, 2019, 5:46 PM
> Subject: Sunsetting Mercurial support in Bitbucket
> To: <dave.tonge at bluespeckfinancial.co.uk <mailto:dave.tonge at bluespeckfinancial.co.uk>>
> After much consideration, we've decided to remove 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.
> What used to be a very fragmented version control software market has rapidly matured. Mercurial usage on Bitbucket is steadily declining, and the percentage of new Bitbucket users choosing Mercurial has fallen to less than 1%. At the same time, Git has become the standard. 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.
> Given that Git has emerged as the version control system of choice for the industry, we have decided to focus our priorities and roadmap on building the best possible experience for the market and our users.
> Read on to learn more about what led to this decision, timeline, and migration resource support.
> Learn more <http://click.mailer.atlassian.com/?qs=1ffd4a36da4e046617308bc62ca08a6b68005bb78aecd4b5bf8ab47aafdb861ec9cd249a8c853f8b1dcbafc5a6d663fee541639aa14c3778>
> You are receiving this email because this is an important message regarding your account and products you are using. You are not allowed to unsubscribe from this type of message.
> <http://click.mailer.atlassian.com/?qs=1ffd4a36da4e0466e0eb3a5e7d24fb39adf3f2aabbc095641ce774df80622dcce8f7a24240fb1a2d730c63a7e2c1f0789768b01dd4bdd8ec> <http://click.mailer.atlassian.com/?qs=1ffd4a36da4e0466b8a7fc02dab2eec1ac2aa5701d10af2b018b2a4604f830fefbcf770d2286fca7b4f4778766ff649b16636faa6d0e5e7e> <http://click.mailer.atlassian.com/?qs=1ffd4a36da4e04665286961c321771f4272789716155a661e1023b31e279e0f952d87125dcb4b275495d7a46e50d1fb0e1f6743dfe39ee3e>
> Copyright 2019 Atlassian Pty Ltd. All rights reserved. We are located at 341 George Street, Sydney, NSW, 2000, Australia
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openid-specs-mobile-profile