Releases for centos6 and centos7
Closed this issue · 4 comments
It would be ideal to provide releases, so projects may specify which version of WunderMachina they want to pull (and therefore knows that is compatible to its project).
It seems that we have two major branches, centos6 and centos7. We could have releases for each branch as following example:
- centos6-1.2.3
- centos7-1.2.3
We also need to discuss that if this can be done, what type of changes is allowed to change the each version segment. I would prefer to follow semantic version standard here.
+1 to this. This would force us to test each release before we make it public, creating more stability for developers in projects. Yes it might slow down the speed at which improvements propagate to all projects, with the benefit of less headache caused by surprises from upstream.
+1
I see the point and was really thinking how to implement this. But after all I think this might lead to counter the original idea of propagating changes etc. and also create maintenance overburden when there are for example security fixes that should be pushed down to all projects immediately.
Also there is already the possibility to pin the specific commit to be used within project and the update / versioning mechanism with critical changes notified through the update checks.
So to sum it up: yes we can start using tags, but pinning projects to those is not engouraged and by using them you agree to keep your project secure.
For the versioning scheme we can use base os as major version, follow the version numbering in changelog for minor changes and finally optional patch for changes that do not require user actions on project side.
I have tagged current tips of both branches now with appropriate tags.