Skip to content

Bump version to v0.30 #210

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

Merged
merged 3 commits into from
Dec 20, 2024
Merged

Bump version to v0.30 #210

merged 3 commits into from
Dec 20, 2024

Conversation

qinsoon
Copy link
Member

@qinsoon qinsoon commented Dec 20, 2024

No description provided.

@qinsoon
Copy link
Member Author

qinsoon commented Dec 20, 2024

@udesou Should we remove v0.29, and start with v0.30 (this PR) as our first release? The alternative is to keep v0.29, and make this a new release v.30. I am okay with either. I will edit the change log file accordingly.

@udesou
Copy link
Contributor

udesou commented Dec 20, 2024

I think it's fine to keep the v0.29 release. I know it's a bit odd because there's no change between these versions but practically, it means that no further change is needed in the upstream-ready/immix branch of the Julia repo about the binding's version.
Except for constantly rebasing the changes from upstream master, that branch should be ready for merging from the binding's perspective (unless something breaks in the meantime).

@qinsoon qinsoon requested a review from udesou December 20, 2024 02:23
Copy link
Contributor

@udesou udesou left a comment

Choose a reason for hiding this comment

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

LGTM.

@qinsoon qinsoon merged commit 102ef81 into mmtk:master Dec 20, 2024
1 check was pending
@udesou udesou mentioned this pull request Jan 1, 2025
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.

2 participants