Skip to content
This repository was archived by the owner on Aug 26, 2022. It is now read-only.

Conversation

@jwhitlock
Copy link
Contributor

  • Add a section explaining why our requirements are complex
  • Make them more complex by adding URLs for code, docs, and changes.
  • Swap regular requirements and constraints sections
  • Update django-tidings from 1.1 to 2.0, which includes support for Django 1.11 and beyond.

I tested this locally by adding a watch and unsubscribing, but didn't send a watch email, which requires a second user. I think this can wait for staging, where I'm subscribed to Ryan's test page.

Add a section explaining why our requirements files are so wordy, and
make them wordier, to include links to code, documentation, and changes
for our third-party libraries.
* django-tidings 1.1 → 2.0: Support Django 1.9 to 2.0, Celery 4.x,
  non-pickle serializer.
@jwhitlock jwhitlock requested a review from escattone February 10, 2018 18:39
Copy link
Contributor

@escattone escattone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work on updating django-tidings as well as this work, thanks @jwhitlock!

@escattone escattone merged commit fc6b3f5 into mdn:master Feb 12, 2018
@jwhitlock jwhitlock deleted the upgrade-django-tidings-1399639 branch February 12, 2018 22:15
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants