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

Sean Hammond sean.hammond at okfn.org
Thu Jan 17 11:29:04 UTC 2013


I agree. I think to keep it simple and consistent our recommendation
should just be that extension branches track the CKAN master and release
branches, even though in reality, very new or simple extensions will
probably only have the one master branch (but by the time they have
conditional behaviour like googleanalytics does, we should just
recommend them to use the branches).

We'll have to change the install instructions in the README file of each
extension, and probably mention it for extension authors in the 'writing
extensions' sphinx docs too.




More information about the ckan-dev mailing list