Issue tracker of sprint work

[hongchaodeng]

I'm creating this issue for tracking progress and coordinating ongoing work:

• Define Core Scope Network: https://github.com/microsoft/hydra-spec/issues/129, https://github.com/microsoft/hydra-spec/pull/140
• Define Core Scope Health: https://github.com/microsoft/hydra-spec/issues/129, https://github.com/microsoft/hydra-spec/pull/133
• Define applicationScopes binding with Component in Configuration: https://github.com/microsoft/hydra-spec/issues/130, https://github.com/microsoft/hydra-spec/pull/135
• Instantiation of Application Scopes should not be bound to Application Configuration: https://github.com/microsoft/hydra-spec/issues/144, https://github.com/microsoft/hydra-spec/pull/147
• dependency story: https://github.com/microsoft/hydra-spec/issues/171
• Define Trait ExposedEndpoint: https://github.com/microsoft/hydra-spec/issues/128
• Support Different Volume Source Define Trait VolumeMounter: https://github.com/microsoft/hydra-spec/issues/91
• Support Component Ordering and Information Passing: https://github.com/microsoft/hydra-spec/issues/23
• Define Scope for Application Metadata: https://github.com/microsoft/hydra-spec/issues/87
• Define Stateful Workload: https://github.com/microsoft/hydra-spec/issues/97
• "example-first" better tutorials for the spec: https://github.com/microsoft/hydra-spec/issues/121, https://github.com/microsoft/hydra-spec/pull/190

[hongchaodeng]

cc @resouer @wonderflow

[suhuruli]

Should we use the Projects board for this?

[wonderflow]

Projects board may be more comfortable, we could use this until next time we need to do the same thing

[hongchaodeng]

Closing since the rest should be tracked in regular release roadmap