Productization process and docs are a bit scattered. We should take some time to clean stuff up, refactor/move content, and make as much as possible fully public in https://github.com/redhat-developer/devtools-productization

• JIRA processes - Revisit CRW-63 and formalize that into a doc rather than a hidden comment inside a JIRA

See https://github.com/redhat-developer/devtools-productization/blob/master/codeready-workspaces/processes/issue-tracking.md

• Document CRW 2.x milestone startup procedures:
  • schedule planning session w/ PM to determine key deliverables
  • determine schedule for RC1, RC2, Quiet Period, QE signoff, Push to stage, Push to prod & GA announce
  • socialize schedule to flush out any conflicts (PTO, conferences, etc.); send to PgM when resolved (2 weeks later?)
  • new AIO Epic issue in JIRA to capture key deliverables
  • new release version in JIRA (fixversion for epic AIO issue)
  • new RCM ticket to request change to Errata (add new product release version)
  • new Errata created
  • run script to update Dockerfiles / VERSION files to new version

See https://github.com/redhat-developer/devtools-productization/blob/master/codeready-workspaces/processes/new-release-milestone-start.md

• CRW image productization process - https://docs.google.com/document/d/1fIrmpSYtYJ1DIo2OLAIW6aC2esGzgH1vjsaB4oHQi1Q/edit

See https://github.com/redhat-developer/devtools-productization/blob/master/codeready-workspaces/processes/new-image-productization.adoc

TODOs

Revisit these older docs and migrate them to the new repo at https://github.com/redhat-developer/devtools-productization/tree/master/codeready-workspaces/

• Private devdoc guides (asciidoc) - TO MOVE as much as possible to public - https://github.com/redhat-developer/codeready-workspaces-productization/tree/master/devdoc

• CRW overall Productization Process (slides) - push PDF to the above repo - https://docs.google.com/presentation/d/1R9tr67pDMk3UVUbvN7vBJbJCYGlUsO2ZPcXbdaoOvTs/edit#slide=id.g4cd0aeeeb5_0_0