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
+3-15
Original file line number
Diff line number
Diff line change
@@ -290,24 +290,12 @@ Overall steps for releasing are covered in the
290
290
To create a release _build_, follow the steps outlined in the [release plan](https://github.com/Microsoft/vscode-python/labels/release%20plan) (which has a [template](https://github.com/Microsoft/vscode-python/blob/master/.github/release_plan.md)).
291
291
292
292
## Development Build
293
+
If you would like to use the latest version of the extension as committed to `master` that has passed our test suite, then you may set the `"python.insidersChannel"` setting to `"daily"` or `"weekly"` based on how often you would like the extension to check for updates.
293
294
294
-
We publish the latest development
295
-
build of the extension onto a cloud storage provider.
296
-
If you are interested in helping us test our development builds or would like
297
-
to stay ahead of the curve, then please feel free to download and install the
298
-
extension from the following
295
+
You may also download and install the extension manually from the following
* Does not get updated with new development builds of the extension (if you want to
311
-
test a newer development build, uninstall the old version of the
312
-
extension and then install the new version)
313
-
* Is built every time a PR is committed into the [`master` branch](https://github.com/Microsoft/vscode-python).
301
+
to install the extension. Do note that the manual install will not automatically update to newer builds unless you set the `"python.insidersChannel"` setting (it will get replaced with released versions from the Marketplace once they are newer than the version install manually).
0 commit comments