Create proposal for Package Repository Processes

[seemiller]

Feature Request

TCE needs to define a process and methodology for handling repositories of packages.

Current Situation

• The process to create a package containing some third party application/functionality has already been defined in the TCE design documentation.
• This package will represent a specific version of that application/functionality.

Consider

• What happens when that application/functionality releases a new version?
  • 
• What is the prescribed process that TCE will use to make available that new version?
• How many package versions will TCE support.?
  • If N=$current_version, will we support n-2?
  • Does N represent major? minor? patch?
• Can multiple versions of a package be available simultaneously?
• How will TCE respond to CVE's in existing packages?
• What channels should TCE provide for its repository (e.g. stable, beta. alpha)
• How we are going to think about "true" community-owned repositories
  • Users will not always want their software to become part of core TCE. We need to provide guidance on how folks can bring their own packages + bring their own package repositories.

Desired State

• To have a document that defines TCE's approach to versioning packages and publishing package repositories.