Create a roadmap for next release

[hongchaodeng]

We need to create a roadmap to involve community members and contributors into development activities in clear direction.

[vturecek]

Here are a few big things that we still need to tackle:

• Upgrade and deployment scenarios. How do we model canary, B/G, A/B scenarios?
• Edge application modeling (#181)
• Modeling non-container and extended workload types (processes, external services)
• Component policies for traits and other operational things (#153)
• Standard definitions for common traits and scopes

I'm sure that I'm missing a few big things here, but this list alone gives us plenty to think about.

[vturecek]

Borrowing from @hongchaodeng's issue tracking (#131)

• Networking model: Container port mapping (#128) and application scope-wide ingress point (#195)
• Volume mapper standard trait definition (#91)
• Support Component Ordering and Information Passing: #23
• Define Scope for Application Metadata: #87
• Define Stateful Workload: #97

[macolso]

• Monitoring scope or trait: Rudr =#223, #76; OAM = #226

[mikkelhegn]

• Parameters overrides and passing information between components: #1 #169 #170

[iyyappam]

Secrets as a first-class resource in the model.