Skip to content

Commit 7c758d1

Browse files
committed
Update release instructions
1 parent 0d26241 commit 7c758d1

File tree

1 file changed

+11
-17
lines changed

1 file changed

+11
-17
lines changed

CONTRIBUTING.md

Lines changed: 11 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -90,31 +90,25 @@ If you're on the core team, you can release Bugsnag as follows:
9090
9191
## Making a release
9292
93-
* Update the version number in setup.py
94-
* Update the CHANGELOG.md, and README.md if necessary
95-
* Commit
93+
* Create branch for the release
9694
9795
```
98-
git commit -am v4.x.x
96+
git checkout -b release/v4.x.x
9997
```
10098
101-
* Tag the release in git
102-
103-
```
104-
git tag v4.x.x
105-
```
106-
107-
* Push to git
99+
* Update the version number in [`setup.py`](./setup.py) and `bugsnag/notifier.py`(./bugsnag/notifier.py)
100+
* Update the CHANGELOG.md and README.md if necessary
101+
* Commit and open a pull request into `master`
102+
* Merge the PR when it's been reviewed
103+
* Create a release on GitHub, tagging the new version `v4.x.x`
104+
* Push the release to PyPI
108105
109106
```
110-
git push origin master && git push --tags
107+
git fetch --tags && git checkout tags/v4.x.x
108+
python setup.py sdist bdist_wheel
109+
twine upload dist/*
111110
```
112111
113-
* Push the release to PyPI
114-
115-
python setup.py sdist bdist_wheel
116-
twine upload dist/*
117-
118112
## Update docs.bugsnag.com
119113
120114
Update the setup guides for Python (and its frameworks) with any new content.

0 commit comments

Comments
 (0)