I have not seen any documentation or guidelines on npm package management concerning deprecations. Within the last, so many releases that I have performed, I have not once deprecated a package.
From our previous stances on version support, we typically only support the current major release. In this discussion, I want to define a process to ensure we properly deprecate our older packages. When we release a patch, minor, or major, we should deprecate accordingly. Using our previous stance in version support, I believe we should follow guidelines as such: * When releasing a patch, deprecate the last patch release within the same subset. * When releasing a minor, nothing happens. * When releasing a major, deprecate the entire previous major (including patches and minors). E.g. Follows in liner time: 1.0.0 release 1.1.0 release 1.2.0 release 1.2.1 release & 1.2.0 deprecated 1.2.2 release & 1.2.1 deprecated 2.0.0 release & 1.1.0 deprecated, 1.2.2 deprecated I will start a vote within 12-24 hours after keeping this discussion thread open for any feedback, modifications, or additions. Additional notes to be prepared on: I will be creating a separate discussion thread & vote for actually deprecating the existing out-dated npm package. Most of or all of our existing out-dated packages are not deprecated. For example, Cordova CLI from version `0.0.1` -> `9.0.0` are still active. This separate discussion thread will include nightlies & also auto deprecation for nightlies. Expect this in another thread to be coming.
