Page Comparison

...

Our code that is marked deprecated already
- Using Python's built-in deprecation warnings
  - https://docs.python.org/2/library/exceptions.html#exceptions.DeprecationWarning
- How can we focus on removing this so that we can see Django's deprecation warnings
  - Jenkins can't handle that many deprecation warnings (mostly)
- Count the number of deprecation warnings and ensure that the number only ever go down.
  - A ticket exists on the TE backlog (Jeremy Bowman (Deactivated) will add a link later)
    Jira Legacy
    server System JIRA
    serverId 13fd1930-5608-3aac-a5dd-21b934d3a4b4
    key TE-2788
Bad imports preventing us from removing sys.path nonsense
Advocate usage of the OEP and propose changes when the process described is not useful
- https://github.com/edx/open-edx-proposals/blob/master/oeps/oep-0021-proc-deprecation.rst
Adding dates to the DeprecationWarning to indicate when we expect things to no longer work
Organizational focus on eliminating warnings
Bubbling up dates into code/tickets so that product can respond
Keep track of deprecation tickets that will impact the next release
- Could be wiki page, could be Jira filter
Examples of situations:
- Dynamic Pacing
  - We will deliver the feature
  - Engineering work needs to happen as part of delivering the feature before we can move onto other projects
Percentage of engineering time dedicated to it
- Dedicate a day or two to engineering work per sprint
Escalation teams - can they take on debt work?

...

Versions Compared