Merge remote-tracking branch 'upstream/master'

* upstream/master:
  Update the TPN (#415)
  0.9.0 release details (#407)

CODING_STANDARDS.md

@@ -2,19 +2,20 @@
 * The following standards are inspired from [Coding guidelines for TypeScript](https://github.com/Microsoft/TypeScript/wiki/Coding-guidelines).
 
 ### Names
-* Use PascalCase for type names.
-* Use "I" as a prefix for interface names only when an interface is implemented by a class.
-* Use PascalCase for enum values.
-* Use camelCase for function names.
-* Use camelCase for property names and local variables.
-* Do not use "_" as a prefix for private properties (unless used as backing properties).
+
+* Use `PascalCase` for type names.
+* Use `I` as a prefix for interface names only when an interface is implemented by a class.
+* Use `PascalCase` for enum values.
+* Use `camelCase` for function names.
+* Use `camelCase` for property names and local variables.
+* Do not use `_` as a prefix for private properties (unless used as backing properties).
 * Use whole words in names when possible.
 
 ### Types
 
 * Do not export types/functions unless you need to share it across multiple components.
 * Do not introduce new types/values to the global namespace.
-* Shared types should be defined in 'types.ts'.
+* Shared types should be defined in `types.ts`.
 Within a file, type definitions should come first.
 
 ### null and undefined
@@ -41,6 +42,6 @@ Use single quotes for strings.
     * `if (x < 10) { }`
     * `function f(x: number, y: string): void { }`
 
-* `else` goes on a the same line from the closing curly brace.
+* `else` goes on the same line from the closing curly brace.
 * Use 4 spaces per indentation.
 * All files must end with an empty line.

CONTRIBUTING.md

@@ -123,18 +123,20 @@ time-critical as a new feature may be.
     [issues awaiting validation](https://github.com/Microsoft/vscode-python/issues?q=label%3A%22awaiting+4-validation%22+is%3Aclosed)
     & validate they have been fixed (and not subsequently broken by
     later changes)
+  * Update the
+    [changelog](https://github.com/Microsoft/vscode-python/blob/master/CHANGELOG.md)
+  * Create a branch for the release
+  * Unfreeze the `master` branch
   * Make sure the
     [documentation](https://code.visualstudio.com/docs/python/python-tutorial)
     -- including the
-    [WOW](https://code.visualstudio.com/docs/languages/python) page)
+    [WOW](https://code.visualstudio.com/docs/languages/python) page
     -- has [appropriate pull requests](https://github.com/microsoft/vscode-docs/pulls)
-  * Update the
-    [changelog](https://github.com/Microsoft/vscode-python/blob/master/CHANGELOG.md)
-  * Tag the release in git
   * Draft a post for the [team blog](https://aka.ms/pythonblog)
 
 Assuming no last-minute issues, the release should be made public
-later that same week.
+later that same week. After releasing, the previous release's branch
+is turned into a tag and its branch is deleted.
 
 ### Issue triaging
 

README.md

@@ -10,27 +10,31 @@ A [Visual Studio Code](https://code.visualstudio.com/) [extension](https://marke
 * Excellent debugging support (remote debugging over SSH, mutliple threads, django, flask)
 * Running and debugging Unit tests ([unittest](https://docs.python.org/3/library/unittest.html#module-unittest), [pytest](https://pypi.io/project/pytest/), [nose](https://pypi.io/project/nose/), with config files)
 * Execute file or code in a python terminal
-* Local help file (offline documentation)
 * Snippets
 
 ## Quick Start
+
 * Install the extension
 * optionally install `ctags` for Workspace Symbols, from [here](http://ctags.sourceforge.net/), or using `brew install ctags` on macOS
 * Select your Python interpreter
   + If it's already in your path then you're set
-  + Otherwise, to select a different Python Interpreter/Version (or use a virtual environment), use the command `Select Workspace Interpreter`)
+  + Otherwise, to select a different Python interpreter/version/environment (use the command `Select Workspace Interpreter` or look in the status bar)
 
 ## [Documentation](https://code.visualstudio.com/docs/languages/python)
+
 For further information and details continue through to the [documentation](https://code.visualstudio.com/docs/languages/python).
 
-## Issues, Feature Requests, and Contributions
-* If you come across a problem with the extension please [file an issue](https://github.com/microsoft/vscode-python)
+## Questions, Issues, Feature Requests, and Contributions
+
+* If you have a question about how to accomplish something with the extension, please [ask on Stack Overflow](https://stackoverflow.com/questions/tagged/visual-studio-code+python)
+* If you come across a problem with the extension, please [file an issue](https://github.com/microsoft/vscode-python)
 * Contributions are always welcome! Please see our [contributing guide](https://github.com/Microsoft/vscode-python/blob/master/CONTRIBUTING.md) for more details
 * Any and all feedback is appreciated and welcome!
   - If someone has already [file an issue](https://github.com/Microsoft/vscode-python) that encompasses your feedback, please leave a 👍/👎 reaction on the issue
   - Otherwise please file a new issue
 
 ## Feature Details
+
 * IDE-like Features
   + Automatic indenting
   + Code navigation ("Go to", "Find all" references)
@@ -78,7 +82,17 @@ For further information and details continue through to the [documentation](http
 ![Unit Tests](https://raw.githubusercontent.com/microsoft/vscode-python/master/images/unittest.gif)
 
 
+## Supported locales
+
+The extension is available in multiple languages thanks to external
+contributors (if you would like to contribute a translation, see the
+[pull request which added simplified Chinese](https://github.com/Microsoft/vscode-python/pull/240)):
+
+* `en`
+* `zh-cn`
+
 ## Data/Telemetry
+
 The Microsoft Python Extension for Visual Studio Code collects usage
 data and sends it to Microsoft to help improve our products and
 services. Read our