Opened 6 years ago

Closed 4 years ago

#3264 enhancement closed worksforme (worksforme)

Summarize deprecation policy for Twisted developers

Reported by: jml Owned by:
Priority: normal Milestone:
Component: release management Keywords: deprecation-policy, documentation
Cc: thijs, jesstess Branch:
Author: Launchpad Bug:

Description

The new deprecation policy (see #3263) needs to be summarized for people who work on Twisted. A good place to put this summary is in the coding standard.

I'm not sure if we have a checklist for reviewers -- if we do, it should go there also.

Change History (9)

comment:1 follow-up: Changed 6 years ago by jml

It should answer questions:

  • How do I add a deprecation?
  • When can I remove it?

comment:2 Changed 6 years ago by thijs

  • Cc thijs added
  • Owner changed from jml to thijs
  • Status changed from new to assigned

comment:3 in reply to: ↑ 1 Changed 6 years ago by thijs

  • Keywords review added
  • Owner thijs deleted
  • Status changed from assigned to new

Replying to jml:

It should answer questions:

  • How do I add a deprecation?
  • When can I remove it?

Putting it up for review so somebody can take a shot at answering these questions so they can be documented.

comment:4 Changed 5 years ago by mwh

This approach doesn't seem to be working.

comment:5 Changed 5 years ago by jml

  • Keywords review removed

There isn't anything to review here, and as mwh said, putting it up for review in order to get answers doesn't seem to be working either. Removing the 'review' tag.

comment:6 Changed 5 years ago by jesstess

  • Cc jesstess added

comment:7 Changed 5 years ago by exarkun

I added <http://twistedmatrix.com/trac/wiki/CompatibilityPolicy#HowtodeprecateAPIs>. It's not great, it's probably wrong and/or incomplete. It's a start, though. We can work on it on the wiki for a while and then turn it into something for the coding standard, I guess.

comment:8 Changed 4 years ago by frap

  • Resolution set to worksforme
  • Status changed from new to closed

I´ve read the deprecate API wiki. Seems to me to make sense. I think we should close this ticket and any enhancements just work through updating the wiki instead of raising tickets for simple docs - as clutters ticket system and adds unneccesary overhead that takes longer than reading and editing the wiki

comment:9 Changed 4 years ago by <automation>

Note: See TracTickets for help on using tickets.