Skip to content

Commit 2a94c3d

Browse files
authored
Update RELEASING.md (#2177)
1 parent 65528f7 commit 2a94c3d

File tree

1 file changed

+0
-10
lines changed

1 file changed

+0
-10
lines changed

RELEASING.md

Lines changed: 0 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -73,16 +73,6 @@ run eachdist once again:
7373
./scripts/eachdist.py update_versions --versions stable,prerelease
7474
```
7575

76-
## Update website docs
77-
78-
If the docs for the Opentelemetry [website](https://opentelemetry.io/docs/python/) was updated in this release in this [folder](https://github.com/open-telemetry/opentelemetry-python/tree/main/website_docs), submit a [PR](https://github.com/open-telemetry/opentelemetry.io/tree/main/content/en/docs/python) to update the docs on the website accordingly. To check if the new version requires updating, run the following script and compare the diff:
79-
80-
```bash
81-
./scripts/generate_website_docs.sh
82-
```
83-
84-
If the diff includes significant changes, create a pull request to commit the changes and once the changes are merged, click the "Run workflow" button for the Update [OpenTelemetry Website Docs](https://github.com/open-telemetry/opentelemetry-python/actions/workflows/docs-update.yml) GitHub Action.
85-
8676
## Hotfix procedure
8777

8878
A `hotfix` is defined as a small change developed to correct a bug that should be released as quickly as possible. Due to the nature of hotfixes, they usually will only affect one or a few packages. Therefore, it usually is not necessary to go through the entire release process outlined above for hotfixes. Follow the below steps how to release a hotfix:

0 commit comments

Comments
 (0)