Define timeline / process for updating stacks in the public devfile registry - registry.devfile.io

[johnmcollier]

With the public devfile registry, registry.devfile.io, now live and hosting devfiles from the devfile/registry repository, we need to have clearly defined process for updating the stacks in the devfile registry. The staging registry (registry.stage.devfile.io) is updated automatically with each commit to master, but the promotion to production is entirely manual and is up to us to decide when to promote.

• Define (and document) how often scheduled updates to the public (production) registry are made
  • Discussed with @elsony earlier, and agreed once a week, on Fridays, as needed sounds like a good start.
  • Should be documented in devfile/registry's readme
• Define (and document) how requests for emergency / interim updates to production should be made, as well as the criteria for such requests (i.e. a stack is broken)
  • Probably just open an issue in this repository with label area/registry or area/registry.devfile.io?'
  • Should be documented in devfile/registry's readme
• Document steps for devfile services team members to perform the promotion to production