Skip to content

adding support policy for dd-trace-rs#249

Draft
ekump wants to merge 1 commit into
mainfrom
ekump/APMSP-3033-establish-support-policy
Draft

adding support policy for dd-trace-rs#249
ekump wants to merge 1 commit into
mainfrom
ekump/APMSP-3033-establish-support-policy

Conversation

@ekump

@ekump ekump commented Jun 8, 2026

Copy link
Copy Markdown
Collaborator

What does this PR do?

First iteration of a support policy for the repo

Motivation

What inspired you to submit this pull request?

Additional Notes

Anything else we should know when reviewing?

@datadog-prod-us1-4

datadog-prod-us1-4 Bot commented Jun 8, 2026

Copy link
Copy Markdown

Pipelines  Tests

Fix all issues with BitsAI

⚠️ Warnings

🚦 2 Pipeline jobs failed

Check Pull Request CI Status | ensure-ci-success   View in Datadog   GitHub Actions

pr-name | pr_name_lint   View in Datadog   GitHub Actions

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 7b4356d | Docs | Datadog PR Page | Give us feedback!

Comment thread docs/SUPPORT_POLICY.md
- The MSRV is documented in `Cargo.toml` (`rust-version`) and verified in CI on every change.
- The MSRV is **never raised in a patch release**. It may be raised in a major or minor release, and
any increase is called out in the `CHANGELOG.md`.
- Datadog commits to supporting Rust stable releases that are **at least 6 months old**: the MSRV

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should be 1 year old?

@iunanua iunanua left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

We're going to have to get used to the policy :P

Comment thread docs/SUPPORT_POLICY.md
Datadog supports the current major version at the **GA** tier and the immediately previous major
version at the **Maintenance** tier:

| State | Which version | What you get |

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Once this policy is merged, should we include this table with the specific versions for each state in the README? (at least GA and Maintenance versions)

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we should. Although since we don't have any major versions yet I wonder if we'll need something slightly different in the interim.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants