Skip to content

Commit

Permalink
Bump version to v0.22 (#1055)
Browse files Browse the repository at this point in the history
  • Loading branch information
qinsoon authored Dec 21, 2023
1 parent e2951ad commit 79fb0bb
Show file tree
Hide file tree
Showing 4 changed files with 40 additions and 5 deletions.
35 changes: 35 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,38 @@
0.22.0 (2023-12-21)
===

## What's Changed

### API

* Flush mutator buffers in `destroy_mutator` by @k-sareen in https://github.com/mmtk/mmtk-core/pull/1045
* NULL and movement check in process_edge by @wks in https://github.com/mmtk/mmtk-core/pull/1032

### Documentation

* Mention revoking TLABs of all mutators after a GC by @k-sareen in https://github.com/mmtk/mmtk-core/pull/1018
* Add missing docs for the vm module by @qinsoon in https://github.com/mmtk/mmtk-core/pull/1021
* Add missing docs for some util modules by @qinsoon in https://github.com/mmtk/mmtk-core/pull/1024
* Add missing docs for the rest of the util module by @qinsoon in https://github.com/mmtk/mmtk-core/pull/1026
* Add missing docs for the rest of the code base (merge after #1026) by @qinsoon in https://github.com/mmtk/mmtk-core/pull/1028
* Update some stale comments by @k-sareen in https://github.com/mmtk/mmtk-core/pull/1036

### CI

* Use new running scripts in ci-perf-kit by @qinsoon in https://github.com/mmtk/mmtk-core/pull/1005
* Upload perf build and log as artifacts (merge after #1005) by @qinsoon in https://github.com/mmtk/mmtk-core/pull/1011
* Fix multiple issues in recent CI changes by @qinsoon in https://github.com/mmtk/mmtk-core/pull/1014
* Fix CI for OpenJDK nogc config by @qinsoon in https://github.com/mmtk/mmtk-core/pull/1019
* Use ci-perf-kit 0.7.4: ignore runs with unmatched key/value in the logs. by @qinsoon in https://github.com/mmtk/mmtk-core/pull/1025
* Fix Ruby binding test repo checkout by @wks in https://github.com/mmtk/mmtk-core/pull/1048

### Misc

* Post-release dependency version bump for v0.21.0 by @wks in https://github.com/mmtk/mmtk-core/pull/1013
* Introduce MockVM by @qinsoon in https://github.com/mmtk/mmtk-core/pull/1049

**Full Changelog**: https://github.com/mmtk/mmtk-core/compare/v0.21.0...v0.22.0

0.21.0 (2023-11-03)
===

Expand Down
4 changes: 2 additions & 2 deletions Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "mmtk"
version = "0.21.0"
version = "0.22.0"
authors = ["The MMTk Developers <>"]
edition = "2021"
license = "MIT OR Apache-2.0"
Expand Down Expand Up @@ -38,7 +38,7 @@ log = { version = "0.4", features = ["max_level_trace", "release_max_level_off"]
memoffset = "0.9"
mimalloc-sys = { version = "0.1.6", optional = true }
# MMTk macros
mmtk-macros = { version = "0.21.0", path = "macros/" }
mmtk-macros = { path = "macros/" }
num_cpus = "1.8"
num-traits = "0.2"
pfm = { version = "0.1.1", optional = true }
Expand Down
4 changes: 2 additions & 2 deletions docs/team/release.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,15 +32,15 @@ If the current version is `0.X.x`, the new version should be `0.X+1.0`.
The PR should include these changes:

1. Bump version in `Cargo.toml`.
2. Bump version in `macros/Cargo.toml`. Use the new version for the `mmtk-macros` dependency in `Cargo.toml`
2. Bump version in `macros/Cargo.toml`.
3. Update `CHANGELOG.md`:
1. Add a section for the new version number and the cut-off date (when the PR is created)
2. Add change logs for the release. The following shows one convenient way to do it. If there is a better way, we should adopt.
1. Auto generate the list of changes for the release on Github. Click on [`releases`](https://github.com/mmtk/mmtk-core/releases),
then click [`Draft a new release`](https://github.com/mmtk/mmtk-core/releases/new). Enter the new version tag,
and the `Generate release notes` button should be avaialble. Copy the notes as the change logs to `CHANGELOG.md`.
Close the release page without tagging a release.
2. Categorize the changes in `CHANGELOG.md`. We use these categories: Plan, Policy, Allocator, Scheduler, API, Misc.
2. Categorize the changes in `CHANGELOG.md`. We use these categories: Plan, Policy, Allocator, Scheduler, API, Documentation, CI, Misc.
4. Update the pinned Rust version in `rust-toolchain` if necessary.
1. Talk with system admin for our CI machines, and check if there is a newer Rust version that we should be using.
2. If we update to a new Rust version, make necessary changes to the code base.
Expand Down
2 changes: 1 addition & 1 deletion macros/Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
[package]
name = "mmtk-macros"
# the macro crate uses the same version as mmtk-core
version = "0.21.0"
version = "0.22.0"
edition = "2021"
license = "MIT OR Apache-2.0"
description = "MMTk macros provides procedural macros used by mmtk-core."
Expand Down

0 comments on commit 79fb0bb

Please sign in to comment.