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 (Proposal for Hydra Edge Extensions #181)
• Modeling non-container and extended workload types (processes, external services)
• Component policies for traits and other operational things (What if Developer has opinion to Traits? #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 (Proposal: Add ExposedEndpoint Trait #128) and application scope-wide ingress point (Hydra App "Service" ingress construct #195)
• Volume mapper standard trait definition (Support different volume sources for container workload #91)
• Support Component Ordering and Information Passing: component startup ordering #23
• Define Scope for Application Metadata: Where will the Application Metadata be defined #87
• Define Stateful Workload: Add StatefulService extended workload #97

[macolso]

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

[mikkelhegn]

• Parameters overrides and passing information between components: Discussion: Piping information between components #1 Easier way of passing parameters to config or env. or output #169 Define fromParam and fromVar #170

[iyyappam]

Secrets as a first-class resource in the model.