ROADMAP for runtime-tools

[Mashimiao]

Hi everyone,
So far, we don't have a roadmap yet. The result is we are not easy to set privilege for PRs and people may don't know what we are focus on.
With such roadmap, I think we can guide people to complete high privilege features first and we can have clear goals for release.
The following a roadmap draft, any comments are welcome.

v0.2.0
complete bundle validation based on runtime-spec, especially jsonschema.

v0.3.0
unify error output based on RFC

v0.4.0
complete container inside part of runtime validation based on runtime-spec.
Including: container inside environment, as mounts, devices, caps and error return(as @wking said in https://groups.google.com/a/opencontainers.org/forum/#!topic/dev/lSYS7RjDZjI)

v0.5.0
complete container inside part of runtime validation based on runtime-spec.
Including: container outside environment, container lifecycle

v0.6.0
complete config generation

v0.7.0
solve options conflict problem

v0.8.0
solve specerror problem #572

[wking]

I prefer issues on GitHub milestones, which in my experience are less likely to go stake (or maybe they're just less invasive when they go stale ? ;). But your order looks fine to me.

[Mashimiao]

I have made some milestones on Github based on this PR.

[wking]

On Thu, Sep 14, 2017 at 07:07:11PM -0700, Ma Shimiao wrote: I have made some milestones on Github based on this PR.

So this issue can be closed? I expect further milestone creation and assignment can happen inline on other issues/PRs as folks notice the need to add/remove them from (new) milestones.

[Mashimiao]

let's keep it open for more milestone discussions

[liangchenye]

I have an idea about runtime tool process.
We can provide a simple server to:

1. compare with runtime-spec/*.md and runtime-tools/specerror/*.go
   if there were any difference, provides an 'icon' to tell that "there need some updates".
2. search RFC error implementations under runtime-tools
   we can tell how many of them do we already implemented. we can provides an 'icon' to tell
   the percentage just like UT coverage
3. add these two icons (or maybe merge to one icon) to the README.md

@RobDolinMS

[liangchenye]

steps of milestone v0.3.0

1. rebase the specerror framework ; complete rfc code of config.md #458
2. complete other missing RFC error codes
3. fill the implemented RFC error codes and add UT

[liangchenye]

Another requirement to v0.6.0:
we need to sure that every test cases WILL NOT leave bundle or container on the testing system.