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

Switch Releases to CalVer #4120

Closed
7 tasks done
Qalthos opened this issue Jan 23, 2024 · 1 comment
Closed
7 tasks done

Switch Releases to CalVer #4120

Qalthos opened this issue Jan 23, 2024 · 1 comment

Comments

@Qalthos
Copy link
Collaborator

Qalthos commented Jan 23, 2024

Prerequisites

  • This was not already reported in the past (duplicate check)
  • It does reproduce it with code from main branch (latest unreleased version)
  • I include a minimal example for reproducing the bug
  • The bug is not trivial, as for those a direct pull-request is preferred
  • Running pip check does not report any conflicts
  • I was able to reproduce the issue on a different machine
  • The issue is not specific to any driver other than 'default' one

Details

As per this discussion we will be changing releases to CalVer moving forward.

This issue is to track the status of that transition.

@Qalthos Qalthos added new and removed new labels Jan 23, 2024
@xoxys
Copy link

xoxys commented Feb 9, 2024

Is there anything with calver that indicates possible breaking changes? Or should we from now on expect that every non-patch release is potentially breaking?

This got not addressed in this "discussion"... So now every release can contain breaking changes, correct?

In general, posting an announcement in a forum but not interacting with the people that provides feedback is not really a discussion.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants