Hi Markus, Thanks for the detail on this. I think that would be useful, but I don't know how many others would benefit. If I'm the only one, I don't want to create extra work just for my benefit. If just me, I can just watch the commits on that repo you linked to.
Scott On Wed, Sep 16, 2015 at 2:19 AM Markus D?ring <mdoering at gbif.org> wrote: > Hi Scott, > > no there isn?t I?m afraid. We have been careful with changes to the public > API which should have mostly been bug fixes, but sometimes minimal, > backwards compatible changes creeped in too. The API has a major version > number in the URL (v1) and we will change that version when including some > proper changes, e.g. separating names and taxa in the API. > > But I agree it would be good to also document the smaller changes, e.g. > new entries to vocabularies used in searches. > We could probably do that retrospectively by going through the commit > history of the API project: > https://github.com/gbif/gbif-api/commits/master > > Do you think this is useful? > > Markus > > > On 15 Sep 2015, at 22:43, Scott Chamberlain <myrmecocystus at gmail.com> > wrote: > > Hi all, > > Is there a changelog somewhere with noteable changes in the API? I could > follow the Issue tracker I suppose, but curious if there's something like > this https://developers.digitalocean.com/documentation/changelog/ for > this API meant for human consumption. > > Thanks! Scott > > _______________________________________________ > API-users mailing list > API-users at lists.gbif.org > http://lists.gbif.org/mailman/listinfo/api-users > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gbif.org/pipermail/api-users/attachments/20150916/3cc2b462/attachment.html>
