Please tag stable releases about django-page-cms HOT 3 CLOSED

I will start to follow this semantic versioning scheme in addition to the changelog.

Thanks for the input. Can I ask how you use the version number in your deployement? Are you able to tell pip to update a package in this way:

django-page-cms>=1.2.0<1.3.0

Meaning that is take the latest backward compatible package for 1.2?

from django-page-cms.

You can do something like that, but usually I prefer using source checkouts (so I can directly patch & commit if I find a bug):

pip install -e git://github.com/dwaiter/[email protected]#egg=whatever

So it will always stay at that version until I manually update it. Semantic versioning just makes it easier for me to look at the new tag and tell how much is going to break if I update.

I could probably set up something similar to what you described (tell pip to automatically update if it won't break anything) but I'd want to test it anyway to be sure, so it's not a big priority.

from django-page-cms.

Hum I kind of fail on the latest release 1.1.3. I should have incread Y (X.Y.Z) because there was new features. The release should be backward compatible anyway.

from django-page-cms.