-
Notifications
You must be signed in to change notification settings - Fork 247
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
NEWS: add news for v0.28.0 #622
Conversation
NEWS
Outdated
|
||
Features: | ||
|
||
- Refactor blackbox tests to allow for testing with disks with 4k sectors |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/allow for/allow/?
s/testing with/testing/?
NEWS
Outdated
|
||
Bug Fixes: | ||
|
||
- Detect disks with 4k sectors correctly when scanning existing partitions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correctly detect disks with 4k sectors when
NEWS
Outdated
|
||
- Detect disks with 4k sectors correctly when scanning existing partitions | ||
- Fix race between HTTP backoff tests | ||
- Set the minimum config version to the actual minimum required in tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Set the minimum config versions in tests to the actual minimum required
NEWS
Outdated
- Detect disks with 4k sectors correctly when scanning existing partitions | ||
- Fix race between HTTP backoff tests | ||
- Set the minimum config version to the actual minimum required in tests | ||
- Relabel /root as well when relabeling with SELinux enabled |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Relabel /root when SELinux relabeling is enabled
Fixed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We've gotten in the habit of grouping test changes alongside actual Ignition changes. The test changes are not user-facing and add clutter, so I wonder if we should start omitting them or putting them in a separate block.
NEWS
Outdated
|
||
- Correctly detect disks with 4k sectors when scanning existing partitions | ||
- Fix race between HTTP backoff tests | ||
- Set the minimum config versions in tests to the actual minimum required |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Trailing space.
No description provided.