Skip to content

Commit 3220f19

Browse files
author
Mrunal Patel
committed
Merge pull request #435 from wking/roadmap-cleanup
ROADMAP: Remove stale targets (landed PRs, image-spec, ocitools, etc.)
2 parents be76764 + 23e03f9 commit 3220f19

File tree

1 file changed

+0
-48
lines changed

1 file changed

+0
-48
lines changed

ROADMAP.md

Lines changed: 0 additions & 48 deletions
Original file line numberDiff line numberDiff line change
@@ -10,26 +10,6 @@ Listed topics may defer to the [project wiki](https://github.com/opencontainers/
1010

1111
## 1.0
1212

13-
### Digest and Hashing
14-
15-
A bundle is designed to be moved between hosts.
16-
Although OCI doesn't define a transport method we should have a cryptographic digest of the on-disk bundle that can be used to verify that a bundle is not corrupted and in an expected configuration.
17-
18-
*Owner:* philips
19-
20-
### Define Container Lifecycle
21-
22-
Containers have a lifecycle and being able to identify and document the lifecycle of a container is very helpful for implementations of the spec.
23-
The lifecycle events of a container also help identify areas to implement hooks that are portable across various implementations and platforms.
24-
25-
*Owner:* mrunalp
26-
27-
### Define Standard Container Actions (Target release: v0.3.0)
28-
29-
Define what type of actions a runtime can perform on a container without imposing hardships on authors of platforms that do not support advanced options.
30-
31-
*Owner:* duglin
32-
3313
### Container Definition
3414

3515
Define what a software container is and its attributes in a cross platform way.
@@ -46,18 +26,6 @@ Proposal: make it an optional feature
4626

4727
*Owner:* hqhq (was vishh) robdolinms, bcorrie
4828

49-
### Validation Tooling (Target release: v0.3.0)
50-
51-
Provide validation tooling for compliance with OCI spec and runtime environment.
52-
53-
*Owner:* mrunalp
54-
55-
### Testing Framework
56-
57-
Provide a testing framework for compliance with OCI spec and runtime environment.
58-
59-
*Owner:* liangchenye
60-
6129
### Version Schema
6230

6331
Decide on a robust versioning schema for the spec as it evolves.
@@ -66,16 +34,6 @@ Resolved but release process could evolve. Resolved for v0.2.0, expect to revisi
6634

6735
*Owner:* vbatts
6836

69-
### Printable/Compiled Spec
70-
71-
Regardless of how the spec is written, ensure that it is easy to read and follow for first time users.
72-
73-
Part of this is resolved. Produces an html & pdf.
74-
Done
75-
Would be nice to publish to the OCI web site as part of our release process.
76-
77-
*Owner:* vbatts
78-
7937
### Base Config Compatibility
8038

8139
Ensure that the base configuration format is viable for various platforms.
@@ -95,9 +53,3 @@ Ensure that we have lifecycle hooks in the correct places with full coverage ove
9553
Will probably go away with Vish's work on splitting create and start, and if we have exec.
9654

9755
*Owner:*
98-
99-
### Distributable Format
100-
101-
A common format for serializing and distributing bundles.
102-
103-
*Owner:* vbatts

0 commit comments

Comments
 (0)