1. Bitbucket
  2. Public Issue Tracker
  3. master
  4. Issues

Issues

Issue #2414 resolved

API roadmap

James Raybould
created an issue

A roadmap of the upcoming changes to the API would be very welcome. Even just a developers mailing list where info on breaking changes and feedback can be given would be nice.

Developing for the iOS platform there are many hoops I have to jump though and knowledge of an upcoming API change would help me schedule when I submit Issue Bucket for review.

Comments (5)

  1. Erik van Zijst staff

    Hi James,

    We don't really have a strict roadmap for the API, other than that we try to continuously add endpoints to it.

    For every feature we add, we update the online docs (http://confluence.atlassian.com/display/BBDEV/Bitbucket+Developer+Documentation), so one thing you could do it sign up at out Confluence server and set an "email watch" on the Bitbucket space:

    - Create an account on http://http://confluence.atlassian.com/

    - Go to http://confluence.atlassian.com/display/BBDEV

    - Click "Browse" -> "Advanced" -> "Watch this space"

    Also, you might want to pop in our #bitbucket channel on irc.freenode.net and just ask us directly, including any suggestions you have for stuff we should be adding.

    Finally we encourage you to just create issues here in the Bitbucket issue tracker for anything we should look at. Anything at all that would help your client apps better integrate.

    Cheers, Erik

  2. James Raybould reporter

    Thanks for the tips, I was wondering what the best way of adding feature requests to the issue tracker was, is it better to bulk load them under one ticket or add them as individual requests?

    Unfortunately I'm in London and work a full time job so whenever I join the IRC channel the majority of the Bitbucket team have turned in for the night! The problem I have with the API documentation is that it is rarely updated. Granted the new email and invitation API's have been documented but the improvements to the user and repositories haven't.

    I think the biggest thing for me would to just get a heads up for either a change that will break an API or an indication that an improvement is coming so that I know to hold off on submitting an update to the App store.

    Again thanks for your time!

  3. Erik van Zijst staff

    is it better to bulk load them under one ticket or add them as individual requests?

    If they're about individual things, I'd just raise multiple issues (so we can respond and close them separately).

    Granted the new email and invitation API's have been documented but the improvements to the user and repositories haven't.

    The easiest thing to do whenever the doco is unclear, is to just leave a comment on the Confluence page in question. If you have a specific suggestion, just dump it right there. That space is closely watched by us, so that's probably the quickest way, with the added benefit that other users will also see it.

    I think the biggest thing for me would to just get a heads up for either a change that will break an API

    We go to great lengths to ensure backwards compatibility of all APIs. If we do mess up, let us know :)

    or an indication that an improvement is coming so that I know to hold off on submitting an update to the App store.

    If you need a specific feature, bugfix, or improvement, best to raise an issue here. That's easiest for us to keep you in the loop while we are addressing it.

    Cheers, Erik

  4. Log in to comment