Update versioning docs for dd-trace-py #28968
Merged
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
Contributor
Preview links (active after the
|
cswatt
approved these changes
Apr 24, 2025
duncanhewett
approved these changes
Apr 25, 2025
Contributor
duncanhewett
left a comment
duncanhewett
left a comment
There was a problem hiding this comment.
Added a couple of suggestions
2 tasks
Co-authored-by: Duncan Hewett <duncanhewett@users.noreply.github.com>
erikayasuda
commented
Apr 25, 2025
erikayasuda
commented
Apr 25, 2025
brett0000FF
approved these changes
Apr 25, 2025
Co-authored-by: Brett Blue <84536271+brett0000FF@users.noreply.github.com>
erikayasuda
commented
Apr 28, 2025
erikayasuda
commented
Apr 28, 2025
erikayasuda
commented
Apr 29, 2025
Contributor
Author
|
/merge |
|
View all feedbacks in Devflow UI.
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
The expected merge time in
|
dd-devflow
bot
added
mergequeue-status: done
and removed
mergequeue-status: in_progress
labels
erikayasuda
added a commit
to DataDog/dd-trace-py
that referenced
this pull request
Apr 30, 2025
Remove duplicate content that will be migrated to the public docs. PR to update the public docs: DataDog/documentation#28968 ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [x] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
brettlangdon
pushed a commit
to DataDog/dd-trace-py
that referenced
this pull request
May 6, 2025
Remove duplicate content that will be migrated to the public docs. PR to update the public docs: DataDog/documentation#28968 ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [x] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
estherk15
pushed a commit
that referenced
this pull request
May 8, 2025
* update versioning for ddtracepy * Update content/en/tracing/trace_collection/compatibility/python.md Co-authored-by: Duncan Hewett <duncanhewett@users.noreply.github.com> * Update content/en/tracing/trace_collection/compatibility/python.md * Update content/en/tracing/trace_collection/compatibility/python.md * Update content/en/tracing/trace_collection/compatibility/python.md Co-authored-by: Brett Blue <84536271+brett0000FF@users.noreply.github.com> * Update content/en/tracing/trace_collection/compatibility/python.md * Update content/en/tracing/trace_collection/compatibility/python.md * Update content/en/tracing/trace_collection/compatibility/python.md --------- Co-authored-by: Duncan Hewett <duncanhewett@users.noreply.github.com> Co-authored-by: Brett Blue <84536271+brett0000FF@users.noreply.github.com>
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