What does deprecated mean? Package lifecycle and the process of deprecation.
An important part of the process of package lifecycle and package development is not just adding new functions. It's equally important to remove functions. Hadley Wickham shares about the package lifecycle process and what 'deprecation' means for functions. See the full video about the purrr 1.0 release: https://youtu.be/EGAs7zuRutY More about the package lifecycle stages: https://lifecycle.r-lib.org/articles/stages.html Maintaining the house that tidyverse built: https://youtu.be/izFssYRsLZs
image: thumbnail.jpg
Transcript#
This transcript was generated automatically and may contain errors.
So it's really like I think part of the really important part of the process of package lifecycle and package development is not just adding new functions, but it is equally important to remove those functions. And we know that removing functions that used to work is frustrating.
And so we have developed this process, this lifecycle process of deprecation, where it starts with pretty mild warnings and kind of gets progressively aggressive, more and more aggressive over time. We hope this is useful. We hope that this kind of gradually pushes you towards the golden path without like forcing you rudely when you're working on something else to urgently switch something.
And so we have developed this process, this lifecycle process of deprecation, where it starts with pretty mild warnings and kind of gets progressively aggressive, more and more aggressive over time.
But at the same time, we believe that we want these functions to be better. We want these things to have a more consistent, cohesive syntax because that makes it easier for future users. And I think we're doing pretty well. We've certainly got a lot better, I think, at handling deprecations and breakages, but we're certainly still trying, still learning. And if you have any feedback, please let us know.
