Ticket #1216 (assigned enhancement )

Opened 3 years ago

Last modified 3 months ago

Deprecation policy

Reported by: jml Assigned to: jml (accepted)
Type: enhancement Priority: normal
Milestone: regular-releases Component: release management
Keywords: deprecation-policy Cc: radix, spiv, jml, glyph
Branch: Author:
Launchpad Bug:

Attachments

Change History

  2005-09-26 12:25:52+00:00 changed by jml 

It'd be kind of nice if we had a deprecation policy written up.  Doesn't have to
be big and hardcore, but just some notes on what we are aiming for, and some
guidelines on how to get there.

  2005-09-28 12:17:27+00:00 changed by hypatia 

Well, what are people *actually* doing? That's always a good basis for a policy
discussion...

  2005-09-28 12:22:57+00:00 changed by jml 

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 :)

  2005-09-28 12:25:52+00:00 changed by hypatia 

Perhaps with some guidelines to the effect that modules where this is regularly
going on or has recently gone on should be marked unstable?

  2007-01-04 13:24:54+00:00 changed by jml

  • cc changed from radix, spiv, jml, hypatia to radix, spiv, jml, hypatia, glyph
  • keywords deleted
  • 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.

  2007-01-04 19:58:48+00:00 changed by hypatia

  • cc changed from radix, spiv, jml, hypatia, glyph to radix, spiv, jml, glyph

  2007-12-19 22:56:13+00:00 changed by glyph

  • branch deleted
  • author deleted

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.

  2008-03-22 23:28:14+00:00 changed by radix

  • milestone set to twisted-8.0

  2008-03-25 19:20:06+00:00 changed by radix

  • milestone changed from twisted-8.0 to regular-releases

  2008-06-01 04:20:30+00:00 changed by jml

  • owner changed from radix to jml
  • status changed from new to assigned

  2008-06-01 04:22:37+00:00 changed by jml

  • keywords set to deprecation-policy

  2008-06-01 04:34:24+00:00 changed by 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.

  2008-06-01 04:35:08+00:00 changed by jml

#3262 is not part of the deprecation policy work.

Note: See TracTickets for help on using tickets.