Skip to content
This repository was archived by the owner on Jan 15, 2025. It is now read-only.

Commit 534ff34

Browse files
authored
Add bf cli build spec (#864)
* Add bf cli build spec * Update release-streams * Update release-streams * Rename release-streams to release-streams.md
1 parent 47caa7a commit 534ff34

File tree

1 file changed

+57
-0
lines changed

1 file changed

+57
-0
lines changed

specs/release-streams.md

Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
# Daily Build Propsal for Botframework CLI
2+
3+
This proposal describes our plan to publish daily builds for consumption. The goals of this are:
4+
1. Make it easy for developers (1P and 3P) to consume our daily builds.
5+
2. Exercise our release to NPM process frequently, so issues don't arise at critical times.
6+
3. Meet Developers where they are.
7+
8+
Use the [Typescript Team](https://www.npmjs.com/package/typescript) as inspiration, and draft off the work they do.
9+
10+
# Versioning
11+
12+
The tags we use for preview versions are:
13+
* -preview.<yyyymmdd>
14+
* -rc.{0}
15+
16+
Note: use of "." rather than "-" to follow semver2 sorting rules.
17+
18+
# Daily Builds
19+
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 .
20+
Build will be done from master. And triggered only once a day
21+
22+
This means developers could install the cli by running
23+
24+
```
25+
npm i -g @microsoft/botframework-cli@next
26+
```
27+
28+
# RC Builds
29+
Copying what the typescript team does, all our NPM packages would be pushed with the rc tag to NPM manually triggered.
30+
Build will be done from manually selected branch.
31+
Build should be the exact same as daily but with different triggers.
32+
33+
This means developers could install the cli by running
34+
35+
```
36+
npm i -g @microsoft/botframework-cli@rc
37+
```
38+
39+
# Production Release
40+
Once RC is stable the production release will switch the tag from rc to latest.
41+
No new build is needed. Only re tagging latest RC
42+
43+
This means developers could install the cli by running
44+
45+
```
46+
npm i -g @microsoft/botframework-cli
47+
```
48+
49+
# PR Builds
50+
Build should be the exact same as daily triggered on PR commits. No publish should be done.
51+
52+
53+
# Migration from MyGet
54+
55+
1. Initially, our daily builds should go to both MyGet and Azure Devops.
56+
2. Our docs are updated once builds are in both locations.
57+
3. Towards the end of 2020, we stop publising to MyGet.

0 commit comments

Comments
 (0)