create authoritative document within the repo that describes tagging scheme for artifacts

[miabbott]

@wking notes in #201 (comment) that he'd like to have something more than an issue comment to reference as the authority on how we tag our artifacts.

Something like TAGS.md would suffice that describes our tags and when they are used.

[ashcrow]

Is this for tagging container images or release tags in git?

[miabbott]

Tagging container images and other artifacts. I'll update title accordingly.

[wking]

Also, this may be impacted by openshift/installer#281. If we move to focusing on early pivots and oscontainer versions, the installer can stop caring about filtering AMIs and just append use the tag when pulling the oscontainer. It sounds like we're planning on using the same tagging scheme for AMIs and oscontainers, but maybe something to think about when wording the content.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale