olucurious/PyFCM

Being explicit about your versioning strategy

lukeburden opened this issue · 2 comments

lukeburden commented

Hi @olucurious - I'm writing a minimalistic Django FCM lib and would like to set dependencies as relaxed as possible to avoid conflicts with other libs.

From your readme it isn't clear what versioning strategy you're using. Since you introduced backwards incompatible changes in a minor release (1.4.0 up from 1.3.1) I assume you're not using semantic versioning? Is it safe to assume that within minor versions there are not backward compatible changes?

Thanks for your efforts!

olucurious commented

Hi @lukeburden, thank you for your work on the Django lib.
The bump from 1.3.1 to 1.4.0 wasn't really clearly planned out, but I want to assure you that the minor versions are backward compatible, at least from v1.4.0

lukeburden commented

OK, good to know. It'd be sweet if you committed to semver on your main readme! I'll set the deps accordingly. Thanks for your response @olucurious.

  • 👍1