ansible/molecule

Switch Releases to CalVer

Qalthos opened this issue · 1 comments

Qalthos commented

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.

xoxys commented

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.