Skip to content
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

Bump to version v0.9.9 #1352

Merged
merged 1 commit into from
Jul 28, 2023
Merged

Bump to version v0.9.9 #1352

merged 1 commit into from
Jul 28, 2023

Conversation

joe-lawrence
Copy link
Contributor

Updates of interest:
v0.9.9:

  • Support for gcc-13
  • Support for Linux 6.2
  • Support for UBSAN kernels
  • Fix handling of PowerPC cpu features
  • Added RHEL-8.8 and 9.2 integration tests

Updates of interest:
v0.9.9:
- Support for gcc-13
- Support for Linux 6.2
- Support for UBSAN kernels
- Fix handling of PowerPC cpu features
- Added RHEL-8.8 and 9.2 integration tests

Signed-off-by: Joe Lawrence <[email protected]>
@euspectre
Copy link
Contributor

Kpatch tools are mature enough and are widely used today. Perhaps, it is time to set version to 1.0 instead of 0.x?
@joe-lawrence @jpoimboe, what do you think?

Copy link
Contributor

@yhcote yhcote left a comment

Choose a reason for hiding this comment

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

Looks good to me.

@jpoimboe
Copy link
Member

Kpatch tools are mature enough and are widely used today. Perhaps, it is time to set version to 1.0 instead of 0.x? @joe-lawrence @jpoimboe, what do you think?

I'm fine with that. Or we could do 1.0 next time, after the bot closes all the stale bugs.

@joe-lawrence
Copy link
Contributor Author

I was hoping to merge the v0.9.9 tag today, but for v1.0 should we finally remove the deprecated kpatch.ko module? There's a lot of "experimental" type warnings in the README.md as well that could possibly be toned down.

@jpoimboe
Copy link
Member

Makes sense. I can open an issue to track what we want to do for 1.0.

@joe-lawrence joe-lawrence merged commit f594a5c into dynup:master Jul 28, 2023
3 checks passed
@euspectre
Copy link
Contributor

I was hoping to merge the v0.9.9 tag today, but for v1.0 should we finally remove the deprecated kpatch.ko module? There's a lot of "experimental" type warnings in the README.md as well that could possibly be toned down.

Fine by me. Thanks!

Yes, I agree, it is time for kpatch.ko to go away.

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.

4 participants