New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Define and document our deprecation policy #500

Open

2 tasks

njsmith opened this issue Apr 16, 2018 · 1 comment

Labels

Member

njsmith commented Apr 16, 2018 •

edited

Loading

We've just had some discussion of this here on a closed PR; should probably promote it to a real issue :-)

To do:

Decide what our deprecation policy is for now. A reasonable start: deprecated code can be removed as soon as the deprecation warning has been in a release for 1 month

Document this. I guess in contributing.rst and in issue Backwards-incompatible changes - SUBSCRIBE TO THIS THREAD if you use trio! #1?

njsmith mentioned this issue

Rip out TaskLocal objects and fix system task context inheritance. #499

Closed

Contributor

smurfix commented Apr 16, 2018

+1
to be revisited as we get closer to 1.0

Zac-HD mentioned this issue

Better tooling for releases and development #220

Open

oremanj added the project meta label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment