Update README.md to include note on how we release npm packages (#82)

Author: iisa

README.md

@@ -34,6 +34,24 @@ To run the tests in watch mode (for <abbr title="test driven development&
 yarn run test:watch
 ```
 
+## Releasing alpha and production tagged packages to NPM
+### Releasing alpha and test packages
+- Use your Jira ticket to create your namespace.  This will prevent collision as many people can be simultaneously working in the same repository.
+  - run: **`npm version prerelease --preid=wedev-1234`**
+    - this command will help auto-increment your alpha package tags inside your jira ticket namespace. refer to [npm versioning docs](https://docs.npmjs.com/cli/v11/commands/npm-version) & [guides for more info on command options](- this command will help auto-increment your alpha package tags inside your jira ticket namespace)
+  - run: **`npm publish --tag alpha`** our most used development tags are: alpha, canary
+ 
+### Releasing production level package
+We like to create a pull request specifically after the expected changes are merged into the main branch.
+Steps:
+- create PR with version number as branch name. Ex, if the next version is 3.2.1, your git command will be:  `git checkout -b v3.2.1`
+  - in the new branch, run the following: 
+    1. **`git pull --tags`** to fetch all git tags
+    2. **`npm version X.X.X`** to set the new tag WITH the commit git tagged
+    3. **`git push --tags`**
+    4. **`npm publish`**
+- Note: version numbers must start at minimum, with 1 (1.x.x) in order for consumers to automatically receive patch updates (no tags starting with 0, like 0.x.x)
+
 ## Linting with ESLint, Prettier, and Types
 To scan the project for linting errors, run
 ```bash