After a long time working with enyo 2.4.0 it looks like I'm now finally have time to upgrade my current project to a newer enyo version and this seems like as good a time as any to ask a question that's been burning in my mind for some time:
What's up with enyo's release management??
If I check out the website, the latest officially released version is 2.5.1, with 22.214.171.124 as official addendum. Based on this, the stable version to upgrade to would be v126.96.36.199.
However, looking on github, there are already a 2.5.2 tag, there are 2.5.3 pre-release tags but no 2.5.3 release, there are 2.5.4 pre-release tags but no 2.5.4 release and finally pre-releases for version 2.6. Then there are also some 'lite' releases as well, which I have no idea what that means...
So, if go by tags on github, the latest stale release not marked with any dev, pre or rc flags, is 2.5.2.
Perhaps, in light of all the efforts being made to create some more structure around enyo (new docs, efforts to improve community interaction, I think I read something about better testing, etc.) perhaps this would also be a good time to add some structure to enyo's release management?
Perhaps it's a good idea to have some clear messaging on which version is officially supported (including important bug-fixes). Also, maybe some rules on what triggers a version bump from 2.5.x to 2.5.y and what triggers a version bump from 2.x to 2.y?
Intuitively a version bump without dev, pre-release or release-candidate flags would imply:
- updated docs
- updated changelog
- an official public release
- official support (things like emergency bug-fixes such as 188.8.131.52)
If one or more of these things cannot be supplied, I would think it should be a release-candidate at best.
Can someone from the enyo team shed some light on this?