Is killing hg support on their cloud offering next?
Definitely not :-) We’re actually investing in Mercurial and I’ve written a blog post on adding some new features to Bitbucket Cloud:
https://blog.bitbucket.org/2017/03/28/edit-history-with-mercurial-evolve-beta-in-bitbucket-cloud/
Welcome to lobste.rs :) You might want to request a hat.
I work for Atlassian. We have developers working on Mercurial features for Bitbucket Cloud. Here’s an example from a couple of weeks ago:
https://bitbucket.org/site/master/issues/6710/enable-exchange-of-obsolete-evolve-markers#comment-34961456
I like how I both created that issue and then subsequently fixed it :-)
Is that not a standard practice at Atlassian? If so, I’d love to hear more!
He created the issue before he was hired :)
Ah! That makes sense. Thanks.
Is killing hg support on their cloud offering next?
Definitely not :-) We’re actually investing in Mercurial and I’ve written a blog post on adding some new features to Bitbucket Cloud:
https://blog.bitbucket.org/2017/03/28/edit-history-with-mercurial-evolve-beta-in-bitbucket-cloud/
Welcome to lobste.rs :) You might want to request a hat.
I work for Atlassian. We have developers working on Mercurial features for Bitbucket Cloud. Here’s an example from a couple of weeks ago:
https://bitbucket.org/site/master/issues/6710/enable-exchange-of-obsolete-evolve-markers#comment-34961456
I like how I both created that issue and then subsequently fixed it :-)
Is that not a standard practice at Atlassian? If so, I’d love to hear more!
He created the issue before he was hired :)
Ah! That makes sense. Thanks.