OpenTreeMap is a collaborative platform for crowdsourced tree inventory, ecosystem services calculations, urban forestry analysis, and community engagement.
[ ] django-hstore - Doesn't support Django 1.10+ and is currently unmaintained. We switched away from using it in https://github.com/OpenTreeMap/otm-core/pull/3124 but it is still in our requirements.txt and is referenced from a migration. Do we need to squash migrations to update?
It is referenced in our initial treemap migration. I believe the only safe way to remove it and not break open source users using code older than f7b4ede9 is to squash migrations.
Because we no longer reference it, it is safe to leave the old version in place.
[x] django-js-reverse (0.7.2 -> 0.7.3) - supports 1.10, unclear if it does or doesn't support 1.11
Commented out with TODOs. We do not use this at runtime so we can just remove it and wait until a compatible version is released.
[x] django-storages - we're using version 1.5. There is support for Django 1.11 in the latest release (1.6), but there are breaking changes
[x] django-threadedcomments (1.0.1 -> 1.1) - supports 1.10, unclear if it does or doesn't support 1.11
[ ] django-url-tools - doesn't support Django 1.9+, currently unmaintained.
Replaced with core code based on the one template tag that we use from this package.
[x] django-tinsel (0.1.1 -> 1.0.0)
[x] django-webpack-loader - we're on 0.3.3, curent version (0.5) lists support for Django 1.11
[x] rollbar - master branch has an unreleased commit fixing a deprecation warning for Django 1.10. Unclear if we need to upgrade, but probably a good idea regardless
jwalgran
commented
7 years ago
Dependencies that will/may need to be updated:
django-apptemplatesdjango-contrib-comments(1.7.3 -> 1.8.0) - 1.8 supports Django 1.11. No breaking changes.django-hstorerequirements.txtand is referenced from a migration. Do we need to squash migrations to update?django-js-reverse(0.7.2 -> 0.7.3) - supports 1.10,unclear if it does or doesn't support 1.11django-queryset-csv- supports 1.10, unclear if it does or doesn't support 1.11django-redis- (4.4.4 -> 4.8.0) 4.8.0 is the latest and appears to support Django 1.11. No listed breaking changes.django-registration-redux(1.4 -> 1.6). There seems to be support for Django 1.11 in the latest release (1.6), but there are breaking changesdjango-statsd-mozilladjango-storages- we're using version 1.5. There is support for Django 1.11 in the latest release (1.6), but there are breaking changesdjango-threadedcomments(1.0.1 -> 1.1) - supports 1.10, unclear if it does or doesn't support 1.11django-url-toolsdjango-tinsel(0.1.1 -> 1.0.0)django-webpack-loader- we're on 0.3.3, curent version (0.5) lists support for Django 1.11rollbar- master branch has an unreleased commit fixing a deprecation warning for Django 1.10. Unclear if we need to upgrade, but probably a good idea regardless