Skip to content

Conversation

@maze88
Copy link
Collaborator

@maze88 maze88 commented Oct 22, 2025

As agreed with Alex.P. We should override patch release doc version changes, by referring to the following format as an example for a patch release (v25.10.x)
For example, Nov changes will be applied to v25.10.x.

This will simplify automation in pipeline New OCP release DOCA driver support.

@github-actions
Copy link

@maze88 maze88 force-pushed the feature/release-notes-with-x-patch branch from 72ba240 to cabbfd5 Compare October 22, 2025 13:10
@rollandf
Copy link
Member

Why is this needed?

@maze88
Copy link
Collaborator Author

maze88 commented Oct 22, 2025

Why is this needed?

added description to PR body.

….10.0-beta.3

task: update documentation for v25.10.0-beta.3
Signed-off-by: Michael Zeevi <mzeevi@nvidia.com>
@maze88 maze88 force-pushed the feature/release-notes-with-x-patch branch from cabbfd5 to ce5c891 Compare October 22, 2025 13:31
* - Version
- Description
* - 25.7.0
* - 25.7.x
Copy link
Member

Choose a reason for hiding this comment

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

I don't think this is a good change.
User will not be able to understand in which patch version a fixed was introduced.

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.

3 participants