Skip to content
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.

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

chore(setuptools_scm): add comment explaining version scheme #8802

Merged
merged 2 commits into from
Mar 28, 2024

Conversation

tabgok
Copy link
Contributor

@tabgok tabgok commented Mar 28, 2024

Checklist

  • Change(s) are motivated and described in the PR description
  • Testing strategy is described if automated tests are not included in the PR
  • Risks are described (performance impact, potential for breakage, maintainability)
  • Change is maintainable (easy to change, telemetry, documentation)
  • Library release note guidelines are followed or label changelog/no-changelog is set
  • Documentation is included (in-code, generated user docs, public corp docs)
  • Backport labels are set (if applicable)
  • If this PR changes the public interface, I've notified @DataDog/apm-tees.
  • If change touches code that signs or publishes builds or packages, or handles credentials of any kind, I've requested a review from @DataDog/security-design-and-guidance.

Reviewer Checklist

  • Title is accurate
  • All changes are related to the pull request's stated goal
  • Description motivates each change
  • Avoids breaking API changes
  • Testing strategy adequately addresses listed risks
  • Change is maintainable (easy to change, telemetry, documentation)
  • Release note makes sense to a user of the library
  • 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

@tabgok tabgok added the changelog/no-changelog A changelog entry is not required for this PR. label Mar 28, 2024
@tabgok tabgok marked this pull request as ready for review March 28, 2024 11:34
@tabgok tabgok requested a review from a team as a code owner March 28, 2024 11:34
@tabgok tabgok requested a review from juanjux March 28, 2024 11:34
@datadog-dd-trace-py-rkomorn
Copy link

Datadog Report

Branch report: teague.bick/DSMS-16/add-semver-comment
Commit report: 1574d2b
Test service: dd-trace-py

✅ 0 Failed, 171368 Passed, 1123 Skipped, 11h 38m 22.74s Total duration (16m 58.56s time saved)

@pr-commenter
Copy link

pr-commenter bot commented Mar 28, 2024

Benchmarks

Benchmark execution time: 2024-03-28 12:37:46

Comparing candidate commit 1574d2b in PR branch teague.bick/DSMS-16/add-semver-comment with baseline commit be880c1 in branch main.

Found 2 performance improvements and 1 performance regressions! Performance is the same for 198 metrics, 9 unstable metrics.

scenario:flasksimple-tracer

  • 🟩 execution_time [-274.361µs; -228.557µs] or [-4.207%; -3.504%]

scenario:httppropagationextract-b3_headers

  • 🟩 max_rss_usage [-709.879KB; -437.820KB] or [-3.271%; -2.017%]

scenario:httppropagationextract-datadog_tracecontext_tracestate_not_propagated_on_trace_id_no_match

  • 🟥 max_rss_usage [+717.321KB; +793.694KB] or [+3.390%; +3.751%]

@tabgok tabgok enabled auto-merge (squash) March 28, 2024 15:09
@tabgok tabgok merged commit a273e1d into main Mar 28, 2024
171 of 173 checks passed
@tabgok tabgok deleted the teague.bick/DSMS-16/add-semver-comment branch March 28, 2024 15:47
christophe-papazian pushed a commit that referenced this pull request Mar 29, 2024
## Checklist

- [x] Change(s) are motivated and described in the PR description
- [x] Testing strategy is described if automated tests are not included
in the PR
- [x] Risks are described (performance impact, potential for breakage,
maintainability)
- [x] Change is maintainable (easy to change, telemetry, documentation)
- [x] [Library release note
guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)
are followed or label `changelog/no-changelog` is set
- [x] Documentation is included (in-code, generated user docs, [public
corp docs](https://github.com/DataDog/documentation/))
- [x] Backport labels are set (if
[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))
- [x] If this PR changes the public interface, I've notified
`@DataDog/apm-tees`.
- [x] If change touches code that signs or publishes builds or packages,
or handles credentials of any kind, I've requested a review from
`@DataDog/security-design-and-guidance`.

## Reviewer Checklist

- [ ] Title is accurate
- [ ] All changes are related to the pull request's stated goal
- [ ] Description motivates each change
- [ ] Avoids breaking
[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
changes
- [ ] Testing strategy adequately addresses listed risks
- [ ] Change is maintainable (easy to change, telemetry, documentation)
- [ ] Release note makes sense to a user of the library
- [ ] 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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog/no-changelog A changelog entry is not required for this PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants