-
Notifications
You must be signed in to change notification settings - Fork 102
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
Conversation
897dcfd
to
a12c97e
Compare
Could you add a changelog entry about #299 for the release? We forgot in that PR 😭 |
92471d1
to
b81d662
Compare
b81d662
to
afeecd1
Compare
Ah, need to re-trigger CI because dialing is too frequent, which results This problem is addressed in rust-vmm/rust-vmm-container#118 |
@rbradford PTAL, this is the prerequisite for |
@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 |
@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]>
Signed-off-by: Ruoqing He <[email protected]>
Signed-off-by: Ruoqing He <[email protected]>
Signed-off-by: Ruoqing He <[email protected]>
afeecd1
to
404ca6d
Compare
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 |
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 🙂 |
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:
git commit -s
), and the commit message has max 60 characters for thesummary and max 75 characters for each description line.
test.
Release" section of CHANGELOG.md (if no such section exists, please create one).
unsafe
code is properly documented.