This is a follow-up on NETOBSERV-107, focusing on process automation for versioning & releasing. See also: https://docs.google.com/document/d/1G85Ro6HWlmUogVjhZh9vM53DVcRgA482_HOEbZttiA0/edit#

Pasting here the relevant content from the doc mentioned above:

Some parts of this workflow can be automated. For instance (suggestion 1) :

• User manually opens a pull request in every repos, containing a changelog update (we will create a changelog file in each repo)
• Prow will watch for PRs with changelog change and validate it is correctly formed (we must make sure that prow will correctly parse the changelog content to extract the new version)
• When merged, Prow performs the git & image building/tagging/pushing

Tag-watching alternative (suggestion 2) :

• User manually (or using a tool installed locally) creates a changelog, opens PR, get it merged in every repos

• User manually applies a tag and push it upstream
• Prow watches for tag change (watches on refs/tags/…) and performs an image build+tag+push