Updating build specs

Author: munozemilio

specs/release-streams.md

@@ -9,15 +9,17 @@ Use the [Typescript Team](https://www.npmjs.com/package/typescript) as inspirati
 
 # Versioning
 
-The tags we use for preview versions are:
-* -preview.<yyyymmdd>
-* -rc.{0}
-
-Note: use of "." rather than "-" to follow semver2 sorting rules. 
+The versioning will be as follow:
+* -dev.<7-digit-commit-SHA>
+* -rc.{Number}
 
 # Daily Builds
-Copying what the typescript team does, all our NPM packages would be pushed with the next tag to NPM on a daily basis at 2am . 
-Build will be done from master. And triggered only once a day
+Copying what the typescript team does, all our NPM packages would be pushed with the next tag to NPM on a daily basis at 12am . 
+(Build)[https://github.com/microsoft/botframework-cli/blob/master/build/botframework-cli-daily.yml] will be done from master. And triggered only once a day. (Release)[https://fuselabs.visualstudio.com/SDK_Public/_release?_a=releases&view=mine&definitionId=7] will be triggered on every time a new build is available.
+
+```
+npm publish [<tarball>|<folder>] --tag next 
+```
 
 This means developers could install the cli by running
 
@@ -28,7 +30,11 @@ npm i -g @microsoft/botframework-cli@next
 # RC Builds
 Copying what the typescript team does, all our NPM packages would be pushed with the rc tag to NPM manually triggered. 
 Build will be done from manually selected branch.
-Build should be the exact same as daily but with different triggers.
+Release should be manually triggered with the selected build.
+
+```
+npm publish [<tarball>|<folder>] --tag rc 
+```
 
 This means developers could install the cli by running
 
@@ -38,7 +44,12 @@ npm i -g @microsoft/botframework-cli@rc
 
 # Production Release
 Once RC is stable the production release will switch the tag from rc to latest.
-No new build is needed. Only re tagging latest RC
+No new build is needed. Only re tagging latest RC.
+Production build should be pointed to the latest stable RC, go through all the packages and re tag them to be latest.
+
+```
+npm dist-tag add <pkg>@<version> latest
+```
 
 This means developers could install the cli by running
 
@@ -47,11 +58,11 @@ npm i -g @microsoft/botframework-cli
 ```
 
 # PR Builds
-Build should be the exact same as daily triggered on PR commits. No publish should be done.
+Build should be triggered on PR commits. No publish should be done.
 
 
 # Migration from MyGet
 
-1. Initially, our daily builds should go to both MyGet and Azure Devops. 
+1. Initially, our daily builds should go to both MyGet and NPM. 
 2. Our docs are updated once builds are in both locations. 
 3. Towards the end of 2020, we stop publising to MyGet.