Skip to content

Conversation

@elfosardo
Copy link
Member

No description provided.

@metal3-io-bot metal3-io-bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jun 19, 2025
@elfosardo
Copy link
Member Author

/cc @tuminoid @Rozzii @lentzi90 @dtantsur

Copy link
Member

@lentzi90 lentzi90 left a comment

Choose a reason for hiding this comment

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

/approve

@metal3-io-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lentzi90

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@metal3-io-bot metal3-io-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 23, 2025
| Operator version | Ironic version(s) | Default version |
| ---------------- | ------------------------------ | --------------- |
| latest (main) | latest, 30.0, 29.0, 28.0, 27.0 | latest |
| 0.4.0 | 30.0, 29.0, 28.0, 27.0 | 30.0 |
Copy link
Member

Choose a reason for hiding this comment

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

0.4.0 still supports latest, it's just not used by default any more

(maybe remove latest from all numbered releases for simplicity?)

Copy link
Member

Choose a reason for hiding this comment

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

I second the latter

Copy link
Member Author

Choose a reason for hiding this comment

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

if we remove latest from old numbered releases, then we'll have to change the default (in code I mean, not just here)
I'm actually wondering if we should just not support any numbered releases below 0.4.0 at this point, and remove them from the scheme
they're all superseded by 0.4.0 anyway

Copy link
Member

Choose a reason for hiding this comment

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

We could have it like this "up to latest" in the Ironic version column, and if at some point we would land a breaking change in the ironic-image then we can just change it to e.g. "up to v40.0" instead of listing all the versions.

Copy link
Member

Choose a reason for hiding this comment

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

Yeah, maybe we remove latest from everywhere except for main. And then add a note that all versions support latest but it's not recommended to use it with any versions or IrSO except for latest.

| 0.1.0 | latest, 27.0 | latest |

**NOTE:** the special version value `latest` always installs the latest
available version of ironic-image and Ironic.
Copy link
Member

Choose a reason for hiding this comment

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

Like, update this note with "This version value is supported by all releases of IrSO but only works reliably in the latest release."

Copy link
Member

@Rozzii Rozzii left a comment

Choose a reason for hiding this comment

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

/lgtm
We have reached a decision on the 2025.07.09 Community meeting.

@metal3-io-bot metal3-io-bot added the lgtm Indicates that a PR is ready to be merged. label Jul 9, 2025
@metal3-io-bot metal3-io-bot merged commit 4d12c04 into metal3-io:main Jul 9, 2025
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants