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

chore: Prepare 0.16.0 release #300

Merged
merged 4 commits into from
Oct 9, 2024
Merged

Conversation

TimePrinciple
Copy link
Contributor

Summary of the PR

Prepare 0.16.0 release to incorporate riscv64 build support, and some minor improvements

Requirements

Before submitting your PR, please make sure you addressed the following
requirements:

  • All commits in this PR have Signed-Off-By trailers (with
    git commit -s), and the commit message has max 60 characters for the
    summary and max 75 characters for each description line.
  • All added/changed functionality has a corresponding unit/integration
    test.
  • All added/changed public-facing functionality has entries in the "Upcoming
    Release" section of CHANGELOG.md (if no such section exists, please create one).
  • Any newly added unsafe code is properly documented.

@roypat
Copy link
Collaborator

roypat commented Oct 7, 2024

Could you add a changelog entry about #299 for the release? We forgot in that PR 😭

CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
@TimePrinciple TimePrinciple force-pushed the prepare-release branch 2 times, most recently from 92471d1 to b81d662 Compare October 7, 2024 08:04
README.md Outdated Show resolved Hide resolved
@TimePrinciple
Copy link
Contributor Author

Ah, need to re-trigger CI because dialing is too frequent, which results Resource unavailable and the like failure :(

This problem is addressed in rust-vmm/rust-vmm-container#118

@TimePrinciple
Copy link
Contributor Author

@rbradford PTAL, this is the prerequisite for linux-loader :)

rbradford
rbradford previously approved these changes Oct 7, 2024
@roypat
Copy link
Collaborator

roypat commented Oct 7, 2024

@rbradford what do you think about merging #278 before the release? It needs a minor bump anyway, so now would be a good opportunity I think

@russell-islam
Copy link
Contributor

@TimePrinciple are you planing to update other rust-vmm crates after this release?

@TimePrinciple
Copy link
Contributor Author

TimePrinciple commented Oct 9, 2024

@TimePrinciple are you planing to update other rust-vmm crates after this release?

Sure thing, what can I help :)

To incorporate:

- [[rust-vmm#287](rust-vmm#287)] Support for RISC-V 64-bit platform.
- [[rust-vmm#299](rust-vmm#299)] atomic_bitmap: support enlarging the bitmap.

Signed-off-by: Ruoqing He <[email protected]>
@russell-islam
Copy link
Contributor

@TimePrinciple are you planing to update other rust-vmm crates after this release?

Sure thing, what can I help :)

In order to use this crate in Cloud-Hypervisor we have to update other crates with this version of vm-memory and create release if necessary, see my recent PRs, Crates are
vhost*, linux-loader, vfio, vfio-user etc.

@TimePrinciple
Copy link
Contributor Author

@TimePrinciple are you planing to update other rust-vmm crates after this release?

Sure thing, what can I help :)

In order to use this crate in Cloud-Hypervisor we have to update other crates with this version of vm-memory and create release if necessary, see my recent PRs, Crates are vhost*, linux-loader, vfio, vfio-user etc.

Noted :) As of vfio (depends on kvm-ioctls) and linux-loader, I was about to integrate RISC-V support in next release, so perhaps these two would take longer. But I will take care of the rest as soon as this is released, would that be acceptable 🙂

@roypat roypat merged commit 4b8649a into rust-vmm:main Oct 9, 2024
2 checks passed
@TimePrinciple TimePrinciple deleted the prepare-release branch October 9, 2024 09:42
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