Skip to content

Wiki update: Steeltoe support policy#1

Open
bart-vmware wants to merge 4 commits intomainfrom
wiki-support-policy
Open

Wiki update: Steeltoe support policy#1
bart-vmware wants to merge 4 commits intomainfrom
wiki-support-policy

Conversation

@bart-vmware
Copy link
Copy Markdown
Owner

@bart-vmware bart-vmware commented Apr 29, 2026

Updates to the Steeltoe support policy. Minor fixes in other markdown files.

The primary changes are:

  • Clarified that only the latest release per major version line receives fixes.
  • Releasing a new minor/patch version does not extend the support window for that major release.

This aligns with what Microsoft and most other .NET OSS projects do.

Under the old terms:

  • Releasing a new minor version of Steeltoe 3.x (to fix CVEs that also introduce breaking changes) would extend the 3.x support window by another year. So as long as new CVEs are found in 3.x, it never reaches end of support.
  • Every minor version of Steeltoe 3.x ever released needs to be patched each time a CVE is found, which we can't properly test because our infrastructure (Tanzu, GitHub Actions, Azure DevOps) isn't compatible with the old versions anymore.

@bart-vmware bart-vmware force-pushed the wiki-support-policy branch 5 times, most recently from 167d89e to bd69d4c Compare May 4, 2026 11:44
@bart-vmware bart-vmware force-pushed the wiki-support-policy branch from bd69d4c to bc03ccc Compare May 4, 2026 12:29
@bart-vmware bart-vmware marked this pull request as ready for review May 4, 2026 12:44
@bart-vmware bart-vmware changed the title Wiki support policy Wiki update: Steeltoe support policy May 4, 2026
Comment thread Home.md
|   4.1.0 | | January 30, 2026 | | .NET 8 - 10 |
|   4.0.0 | | September 4, 2025 | | .NET 8 - 9 |
| **Steeltoe 3** | Active | August 21, 2020 | September 4, 2026 | |
|   3.3.0 | | September 4, 2025 | | .NET 6 - 8 [^1] |
Copy link
Copy Markdown
Collaborator

@TimHess TimHess May 5, 2026

Choose a reason for hiding this comment

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

What are you thinking about EOL for the 3.4 release? Should we special-case it now that it also bumps us up to net8 and support it until net8's EOL (November 10, 2026)?

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

I don't think that makes sense. The rule "one year after the next major version" should provide sufficient time to upgrade. I wouldn't want to imply we'll keep supporting old releases as long as they target a framework that's still supported by Microsoft. Because if we were to release a hypothetical Steeltoe 5 in two months, that would also mean we'll keep Steeltoe 4 in support until .NET 10 is no longer supported. Our release dates and frequency don't align with .NET versions.

Comment thread Steeltoe-Support-Versions.md Outdated
There is a rare chance that we might be forced to break compatibility in a minor release, but we will be sure to be clear of our reasons for doing so.
| Steeltoe Version | Status | Release Date | End of Life Date | .NET Runtime Version |
| --- | --- | --- | --- | --- |
| **Steeltoe 4** | Active | September 4, 2025 | TBD | |
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.

I'm hesitant about TBD with no date or commentary. Perhaps we should add a footnote that states it will be no earlier than Sep 2028, as originally stated?

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

I initially had a date, but Cursor suggested using TBD there because the date is still unknown. It also rejected leaving it empty. Its guidance was based on what other OSS projects generally do.

Is it better now?

Comment thread Home.md
@@ -1,18 +1,14 @@
TEST
Copy link
Copy Markdown
Collaborator

@TimHess TimHess May 5, 2026

Choose a reason for hiding this comment

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

Is this TEST the only difference across these files from the live wiki?

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

No, the diff in this PR shows all changes compared to live.

Comment thread Steeltoe-Support-Versions.md Outdated

When new versions of Steeltoe are released, they are tested with the latest supported versions of .NET.
It is recommended to run the latest patch version for the targeted Steeltoe release.
### Security fixes and serious defect fixes
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.

Fix/fixes is used a lot in this section... we could mix it up with "issues", "patches", etc.

Maybe slightly simpler as "Security issues and serious defects" for the header?

@bart-vmware bart-vmware requested a review from TimHess May 6, 2026 09:00
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