java - What is the "best practice" to remove support for a feature? -
i have library deals several message formats. each of these formats closely related, they're common base xml each has additional constraints or data on top of it.
one of these formats created support proof-of-concept or pilot effort. pilot over, no longer being used, , imposed awkward constraints. i've gotten permission remove support it. correct way this?
i'm thinking:
- open issue track/document changes
- tag svn revision, "feature_x removed here"
- @deprecate specific classes. cite issue. commit.
- watch warnings , see deprecation affects
- let sit bit, give team chance deal deprecation
- finally remove code. verify tests ok. commit.
to steps above, i'd suggest communicate others feature dropped given deadline. , if feature and/or team big, i'll suggest others commitment remove code dependencies date (the bigger team is, more important commitment is, consider managers support task). experience shows, removing big surprise few users, , there somewhere somecode still depends on feature_x. , last not least, additional step dry-run removal, can easy , undone.
Comments
Post a Comment