Details

    • Type: Suggestion
    • Status: Closed (View Workflow)
    • Resolution: Answered
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      As a DVCS user, I would like to take advantage of Bitbucket Server to manage my Mercurial repositories as well as my Git repositories.


      Atlassian status as of March 2017

      Hi everyone,

      Firstly, thanks for your feedback, passion and advocacy for this suggestion. Please accept my apologies for allowing this issue to remain open for some time without clear direction from Atlassian.

      We would love to support the availability of choices when it comes to DVCS-based development in Bitbucket Server. However, we have decided that the engineering cost of adding and maintaining Mercurial support is ultimately the wrong direction to take the product. While it is heartening to see recent developments in Mercurial as an SCM, we have not seen signs of a positive market shift that would justify an investment for Bitbucket Server, especially given strong demand from existing customers for more capabilities based on Git.

      A number of people have offered approaches to make this suggestion a reality for Bitbucket Server, and we've explored and discussed them all. Ultimately, we feel that any commitment to Mercurial would need to be a full commitment; anything else defers future disappointment, as a second-class solution leads to frustration and regret.

      While Bitbucket Server and Bitbucket Cloud offer the same primary code collaboration features, they do have different origins, allowing them to optimize for the needs of their subtly different customer bases. Bitbucket Cloud has a strong foundation as a Mercurial hosting product and has a loyal following that it will continue to support while also investing in a range of other improvements. I reiterate my past recommendations to consider Bitbucket Cloud for Mercurial hosting if the choice between DVCS options is what is most important to you.

      So if we are not going to implement this feature in Bitbucket Server, what are we doing instead? We remain committed to helping software teams deliver high quality software faster in an increasingly competitive and changing world. We believe that great developer tools are a key element of modern software development in the hands of good teams with smart processes. To that end, we've made improvements already and are planning to work in the following areas that help with problems teams face now:

      • scaling to ever larger numbers of users and CI/CD load - security, performance and manageability at scale is baked into everything we do
      • seamless workflow integration between Atlassian and other leading products, bringing together the combined power of best of breed tools
      • innovations that increase team consistency and developer productivity, and reduce complexity despite an ever evolving technology landscape

      Thank you again for your long-standing interest and feedback on this issue. We're confident that the improvements we have planned for Git-based development in Bitbucket Server will unleash the greatest overall potential in software teams around the world, and we look forward to supporting you.

      If you have any questions or concerns feel free to contact me directly.

      Cheers,
      Roger Barnes
      Principal Product Management - Bitbucket Server
      rbarnes |at| atlassian |dot| com

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                stower Simon Tower [Atlassian]
              • Votes:
                546 Vote for this issue
                Watchers:
                303 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: