diff options
Diffstat (limited to 'docs/npm.md')
| -rw-r--r-- | docs/npm.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/npm.md b/docs/npm.md index 01b99ccd..e39debc1 100644 --- a/docs/npm.md +++ b/docs/npm.md @@ -20,7 +20,7 @@ This project follows a structured release process to ensure that all packages ar ## Current Theory -For most all changes, simply patching the minor version is acceptable. We can and should release frequently; the more often we release the easier it is to tell what change broke something. Developeres are encouraged to push a release as described below after their branch merges. I also think I'm open to doing the release publishing steps as a part of an existing PR, though this could have more churn if others are also releasing and version numbers change frequently. +For most all changes, simply patching the minor version is acceptable. We can and should release frequently; the more often we release the easier it is to tell what change broke something. Developers are encouraged to push a release as described below after their branch merges. I also think I'm open to doing the release publishing steps as a part of an existing PR, though this could have more churn if others are also releasing and version numbers change frequently. ## How To Release |