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

v1.0 when ? #104

Open
j-fu opened this issue Jan 23, 2025 · 2 comments
Open

v1.0 when ? #104

j-fu opened this issue Jan 23, 2025 · 2 comments

Comments

@j-fu
Copy link
Collaborator

j-fu commented Jan 23, 2025

Hi, what does everyone think about moving to v1.0. I am in favor of it as in my experience having full semver active eases the handling of things quite a bit.

@mipals
Copy link
Member

mipals commented Jan 23, 2025

I am not against it. Is the reason that MKL2025 dropped 32-bit support? Or is there someting else?

@j-fu
Copy link
Collaborator Author

j-fu commented Jan 23, 2025

The reason is more general as dependency management works better when we have a clear distinction between breaking, feature or bugfix releases. But you are right, #103 should be breaking, so I would vote for 1.0 with this update. Let us see what the other say then.

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

No branches or pull requests

2 participants