To include functionality of #7, as well as to have a console "wizard" like devtools::release() that asks all the questions in the Life Cycle Statement and updates accordingly. Thus each release will conform compliance with current versions of standards (optionally allowing software to remain in current, potentially non-compliant states), and will update lifecycle.md accordingly. Thanks to @karthik for the idea.
mpadge
commented
3 years ago
To include functionality of #7, as well as to have a console "wizard" like
devtools::release()that asks all the questions in the Life Cycle Statement and updates accordingly. Thus each release will conform compliance with current versions of standards (optionally allowing software to remain in current, potentially non-compliant states), and will updatelifecycle.mdaccordingly. Thanks to @karthik for the idea.