Opened 13 years ago
Closed 3 years ago
#1216 enhancement closed fixed (fixed)
Deprecation policy
Reported by: | Jonathan Lange | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | totally automated release infrastructure |
Component: | release management | Keywords: | deprecation-policy |
Cc: | radix, spiv, Jonathan Lange, Glyph | Branch: | |
Author: |
Change History (16)
comment:2 Changed 13 years ago by
Well, what are people *actually* doing? That's always a good basis for a policy discussion...
comment:3 Changed 13 years ago by
I *think* the advice on the street is "Deprecate in Release 2.n, remove in Release 2.(n+1)" Deprecation is done by issuing a DeprecationWarning using the warnings module. This sounds fine to me :)
comment:4 Changed 13 years ago by
Perhaps with some guidelines to the effect that modules where this is regularly going on or has recently gone on should be marked unstable?
comment:5 Changed 12 years ago by
Cc: | Glyph added |
---|---|
Keywords: | documentation removed |
Owner: | set to radix |
glyph says, "We should have a time-based deprecation policy." (See #2352)
Also, having the policy means documenting and enforcing it.
comment:6 Changed 12 years ago by
Cc: | hypatia removed |
---|
comment:7 Changed 11 years ago by
I've written up a proposed compatibility policy. I think the real remaining challenge here is to get our release process back on track so that we can have an official point where it takes effect; and perhaps also to clean up the deprecation warnings listed there.
comment:8 Changed 11 years ago by
Milestone: | → twisted-8.0 |
---|
comment:9 Changed 11 years ago by
Milestone: | twisted-8.0 → regular-releases |
---|
comment:10 Changed 11 years ago by
Owner: | changed from radix to Jonathan Lange |
---|---|
Status: | new → assigned |
comment:11 Changed 11 years ago by
Keywords: | deprecation-policy added |
---|
comment:12 follow-up: 15 Changed 11 years ago by
#3262 #3263 #3264 #3265 and #3266 have all been filed in response to the new thread at: http://twistedmatrix.com/pipermail/twisted-python/2008-April/017497.html
They have all been tagged with "deprecation-policy" and assigned to me.
This ticket is now functioning as the master ticket for the new work. I'm happy to consider #1216 superceded by the new keyword.
comment:14 Changed 8 years ago by
Owner: | Jonathan Lange deleted |
---|
comment:15 Changed 6 years ago by
Description: | modified (diff) |
---|
Replying to jml:
#3262 #3263 #3264 #3265 and #3266 have all been filed in response to the new thread at: http://twistedmatrix.com/pipermail/twisted-python/2008-April/017497.html
They have all been tagged with "deprecation-policy" and assigned to me.
This ticket is now functioning as the master ticket for the new work. I'm happy to consider #1216 superceded by the new keyword.
I've updated the description to reference these tickets so that it'll be a little easier to find them.
comment:16 Changed 3 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |