Add documentation for tracking changes to Django and Wagtail#208
Merged
willbarton merged 1 commit intomasterfrom Jul 27, 2020
Merged
Add documentation for tracking changes to Django and Wagtail#208willbarton merged 1 commit intomasterfrom
willbarton merged 1 commit intomasterfrom
Conversation
willbarton
requested review from
Scotchester,
alexm118,
chosak,
cwdavies,
higs4281 and
schbetsy
willbarton
force-pushed
the
tracking-django-wagtail
branch
from
4e984e9 to
cf5c758
Compare
higs4281
reviewed
Jul 23, 2020
higs4281
approved these changes
Jul 23, 2020
Member
higs4281
left a comment
higs4281
left a comment
There was a problem hiding this comment.
Nicely done. One minor note.
Scotchester
reviewed
Jul 23, 2020
In this change I have attempted to document the process we've undertaken to upgrade Django and Wagtail. I've moved the supported-versions matrix from the Python standard doc and makes it more concrete to apply to Django and Wagtail and cf.gov and its satellites and libraries. I've documented the approach we have been taking to feature detection and version testing, and the actual approach to keeping satellites, libraries, and cf.gov itself up-to-date. It's a little bit ARID with the changes to the Python standards doc and tox, but that's intentional. Co-authored-by: Scott Cranfill <scott.cranfill@cfpb.gov>
willbarton
force-pushed
the
tracking-django-wagtail
branch
from
4f6e4aa to
b450716
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In this change I have attempted to document the process we've undertaken to upgrade Django and Wagtail.
I've moved the supported-versions matrix from the Python standard doc and makes it more concrete to apply to Django and Wagtail and cf.gov and its satellites and libraries.
I've documented the approach we have been taking to feature detection and version testing, and the actual approach to keeping satellites, libraries, and cf.gov itself up-to-date.
It's a little bit ARID with the changes to the Python standards doc and tox, but that's intentional.
I would still like to add more links to GitHub Actions, once I revisit #206 and the GitHub Actions templates, but for now this is a starting point.
You can preview the changes here:
https://github.com/cfpb/development/blob/tracking-django-wagtail/standards/python.md
https://github.com/cfpb/development/blob/tracking-django-wagtail/guides/tracking-django-wagtail.md