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

prepare v9.3.1 #2643

Merged
merged 1 commit into from
Feb 12, 2025
Merged

prepare v9.3.1 #2643

merged 1 commit into from
Feb 12, 2025

Conversation

ReimarBauer
Copy link
Member

Purpose of PR?:
preparing minor release

Copy link
Contributor

@jgrooss jgrooss left a comment

Choose a reason for hiding this comment

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

I only see the version entry in CHANGES.rst and in version .py
This I can approve.
I cannot judge the underlying individual changes in the devel branch.

@ReimarBauer
Copy link
Member Author

I only see the version entry in CHANGES.rst and in version .py This I can approve. I cannot judge the underlying individual changes in the devel branch.

That`s not asked here ;)

I think that's a misunderstanding, I'm doing a patchlevel release here.

To judge whether it should be a patch level or a minor release, you can always look at the link in Changes. Then of course in the changes there. Usually bugfixes are on the patch level. When we can add an enhancement (feature) without an API change then we need to change the minor level.

And the major number to version 10 will happen when we merged develop to stable. Maybe next week.

So thx for the approve.

@ReimarBauer ReimarBauer merged commit 529ce88 into Open-MSS:stable Feb 12, 2025
9 of 10 checks passed
@ReimarBauer ReimarBauer deleted the v9.3.1 branch February 12, 2025 15:06
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.

3 participants