[ckan-dev] Recommended practice for supporting both CKAN 1.8 and 2.0 in extensions

Thu Jan 17 11:25:31 UTC 2013

> The solution we had for this before was to make a branch in the extension
> with the same name as the CKAN release branch that it supports. So in
> googleanalytics we would create branches release-v1.8 and release-v2.0. The
> extension master branch would then be kept up to date with CKAN master.

That sounds very sensible