Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Update the versioning scheme #356

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Dec 6, 2017
Merged

Update the versioning scheme #356

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e61fcd3
Update the versioning scheme
brettcannon Dec 5, 2017
7a10b2e
Actually use the proper year for the example
brettcannon Dec 6, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 15 additions & 20 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
## Contribution
* Please feel free to fork and submit pull requests
# Contributing to the Python extension for Visual Studio Code

## Contributing a pull request

### Prerequisites

Expand All @@ -13,7 +14,7 @@

### Setup

```
```shell
git clone https://github.com/microsoft/vscode-python
cd vscode-python
npm install
Expand All @@ -40,9 +41,10 @@ Use the `Launch Extension` launch option.
Run the Unit Tests via the `Launch Test` and `Launch Multiroot Tests` launch option.
Currently unit tests only run on [Travis](https://travis-ci.org/Microsoft/vscode-python)

_Requirements_
#### Requirements

1. Ensure you have disabled breaking into 'Uncaught Exceptions' when running the Unit Tests
2. For the linters and formatters tests to pass successfully, you will need to have those corresponding Python libraries installed locally
1. For the linters and formatters tests to pass successfully, you will need to have those corresponding Python libraries installed locally

### Standard Debugging

Expand All @@ -59,7 +61,6 @@ From there use the ```Extension + Debugger``` launch option.
Information on our coding standards can be found [here](https://github.com/Microsoft/vscode-python/blob/master/CODING_STANDARDS.md).
We have a pre-commit hook to ensure the code committed will adhere to the above coding standards.


## Development process

To effectively contribute to this extension, it helps to know how its
Expand Down Expand Up @@ -208,17 +209,11 @@ it should have an appropriate `closed-` label.
### Versioning

Starting in 2018, the extension switched to
[calendar versioning](http://calver.org/) from
[semantic versioning](https://semver.org/) since the extension
auto-updates and thus there is no need to care about its version
number in terms of backwards-compatibility. As such, the major version
is the current year, the minor version is the week of the year, and
the micro version is how many releases there have been that week
(starting at 0). For example, a release made on July 2, 2018 would
have a version number of `2018.27.0`. To easily calculate the first
release of a week, you can run the following Python code:
```python
import datetime
year, week, _ = datetime.date.today().isocalendar()
print(f"{year}.{week}.0")
```
[calendar versioning](http://calver.org/) since the extension
auto-updates and thus there is no need to track its version
number for backwards-compatibility. As such, the major version
is the current year, the minor version is the current month, and
the micro version is how many releases there have been that month in
the year (starting at 0). For example, the first release in July 2018
would be `2018.7.0`, the second release that month would be
`2018.7.1`, etc.