On Thu, Aug 04, 2016 at 02:35:29PM -0600, Karl Williamson wrote: > I think we should have a pod that lists the features that are > deprecated, and maybe those that are merely discouraged, when they > gained this status, and when the deprecated ones are scheduled to be > removed, or that there is no current plan to remove them. I think we should eliminate the latter category. Once a feature is deemed to be deprecated, it should get an end-of-life date (major version) attached to it. This makes it clear to the user when it will disappear; it avoids the temptation of "well, I know it's deprecated, but it has been deprecated for eons, I bet it won't disappear anytime soon, let's use it"; and it avoids discussions of how many more cycles we should wait when we finally want to cull it. > This would help us remember to actually do the removals, and be > transparent to our customers. Removals can then happen at a 5.odd.1 release ;-) AbigailThread Previous | Thread Next