Open Grokzen opened 9 years ago
We should be fine with the whole 2014.7.x releases.
salt>0.16.2, salt<=So 2014.7.11
Im not aware of a platform that only has 0.16.x or older available, so im not planning on supporting anything older than that. Generally i think its important, to deprecate things early on and to get rid of lose ends that may result in too much work just to support old versions.
On a side note, i have been running eventsd for a little while now with the latest release currently 2015.5.2 without any problems regarding basic functionality.
@felskrone What is your opinion on pinning the max version of salt that we currently support via future TravisCI tests?
My suggestion would be to change requirements file to the following right now
salt>=0.16.2,<=2014.7.0
and when we have tested a new version or similar we can bump the version number. Or would this cause to many issues with backwards compability on older releases?