Date
Attendees
Goals
- edX-owned django 1.11 dependency upgrade kick off and coordination
Discussion items
| Time | Item | Who | Notes |
|---|
| Timeline | | - Doing the upgrade earlier will help to uncover any issues early and inform the platform's upgrade
- Upgrading the satellite repos blocks the platform upgrade, which in turn blocks the hawthorn release
- Getting this complete by the end of July is the ask
|
| | Coordination | | - Keep platform and dependent repos compatible with django 1.8 & 1.11
- Use tox to enforce this. Some repos don't have this already and it should be added
- This will enable package upgrades to be merged to master
- Many tickets have been assigned to the Learner and Educator teams as the domain experts
- It's possible that not all satellite repos have been found
- HipChat Room for coordination and questions: "Django v1.9/10/11 Upgrade"
- Tag Platform peeps on PRs
|
| Questions |
| - What do you plan to do w/ DRF (e.g. 3.6)?
- The plan is to upgrade, but maybe to go to 3.4 if upgrading to the latest isn't possible
- How we deal with dependencies of satellite repositories?
- Feature teams should ping the Platform team for concerns and updates
- What about IDAs that are still on 1.8?
- Those will be upgraded later and separate from this conversation
- Do we really need this package?
|
Action items
Put them here: Candidates for deprecation post-upgrade