Once we have a stable version of the rewrite published on npm, we envision the following process:
Rename master to legacy.
Rename rewrite to main and make it the default branch.
On the legacy branch, add a banner in the README stating that the module is now deprecated in favor of the new modules.
Publish a new MAJOR release with the README change.
Deprecate the old module on npm (as far as I understand the npm documentation, deprecation only affects latest).
The above process would not break existing builds that depend on a current version of mochify, but it will yield a deprecation warning on new installs of the new major.
If you have more idea, please feel free to comment.
Once we have a stable version of the rewrite published on npm, we envision the following process:
mastertolegacy.rewritetomainand make it the default branch.legacybranch, add a banner in the README stating that the module is now deprecated in favor of the new modules.latest).The above process would not break existing builds that depend on a current version of mochify, but it will yield a deprecation warning on new installs of the new major.
If you have more idea, please feel free to comment.