You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+11-1Lines changed: 11 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -196,15 +196,25 @@ More details for this are [here] (https://devdiv.visualstudio.com/DevDiv/_git/Vi
196
196
## Snapping for releases
197
197
Extension releases on the marketplace are done from the prerelease and release branches (corresponding to the prerelease or release version of the extension). Code flows from main -> prerelease -> release. Every week we snap main -> prerelease. Monthly, we snap prerelease -> release.
198
198
199
+
### Versioning Scheme
200
+
The extension follows a specific versioning scheme for releases:
201
+
-**Prerelease versions**: Use standard minor version increments (e.g., 2.74, 2.75, 2.76...)
202
+
-**Stable release versions**: Use the next tens version (e.g., 2.74 prerelease becomes 2.80 stable)
203
+
-**Main branch after RC snap**: Jumps to one above the next stable version (e.g., if snapping 2.74 as RC, main becomes 2.81)
204
+
199
205
### Snap main -> prerelease
200
206
The snap is done via the "Branch snap" github action. To run the snap from main -> prerelease, run the action via "Run workflow" and choose main as the base branch.
When running the snap action, you can optionally check the "Is this a release candidate snap" checkbox. If checked:
210
+
- The prerelease branch will receive the snapped code with the current version (e.g., 2.74)
211
+
- The main branch version will be updated to be higher than the next stable release (e.g., 2.81, since the next stable would be 2.80)
212
+
203
213
This will generate two PRs that must be merged. One merging the main branch into prerelease, and the other bumps the version in main.
204
214

205
215
206
216
### Snap prerelease -> release
207
-
To snap from prerelease to release, run the same action but use **prerelease** as the workflow branch. This will generate a single PR merging from prerelease to release.
217
+
To snap from prerelease to release, run the same action but use **prerelease** as the workflow branch. This will generate a PR merging from prerelease to release, and automatically update the version to the next stable release version (e.g., 2.74 -> 2.80) on the merge branch before the PR is merged.
208
218
209
219
### Marketplace release
210
220
The marketplace release is managed by an internal AzDo pipeline. On the pipeline page, hit run pipeline. This will bring up the pipeline parameters to fill out:
0 commit comments