Update versioning docs for dd-trace-py #28968
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Preview links (active after the
|
cswatt
approved these changes
Apr 24, 2025
duncanhewett
approved these changes
Apr 25, 2025
2 tasks
Co-authored-by: Duncan Hewett <[email protected]>
erikayasuda
commented
Apr 25, 2025
erikayasuda
commented
Apr 25, 2025
brett0000FF
approved these changes
Apr 25, 2025
Co-authored-by: Brett Blue <[email protected]>
erikayasuda
commented
Apr 28, 2025
erikayasuda
commented
Apr 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
The versioning docs for dd-trace-py haven't been updated for 3 years. This is the start of a larger process to migrate our contributor/readthedocs docs over to the public docs as much as possible.
Once this is merged, we will merge a subsequent PR on the dd-trace-py side to delete the duplicate information and just provide a link to the public docs instead (DataDog/dd-trace-py#13269).
Merge instructions
Merge readiness:
For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes