Open mvdbeek opened 8 years ago
Ah, forget about it. If we are just replacing a release with commits I think this just makes things more complicated (as someone needs to do this) but if we can extend this to have bugfixes for releases I think this would be nice.
Example, currently if we release a new Docker version, I hardly can update the roles because they usually contain also new features and not only bugfixes and potentially break more than they fix. A release which I can bugfix later on would be nice. But as usual I fear the complexity involved.
I'm okay with doing this - especially in light of #130. Is there still an appetite for this?
Maybe we could at least have release branches, where you could do bug fixes on top later on, without having the extra burden of a proper release process (and having to have someone to take care of them). By proper release I mean that you publish this in ansible galaxy with a specified version (where I can see there is burden), or do you had something else in mind for a release?
I publish mine to Ansible Galaxy so they do have tagged versions.
I would like to start making releases for all of the galaxyproject ansible roles, so that we can reference a release instead of a commit when specifying these roles as dependencies. Is that OK for everyone? ping @afgane @bgruening @jmchilton @natefoo @dannon