Skip to content

ROADMAP: Remove stale targets (landed PRs, image-spec, ocitools, etc.) #435

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mrunalp merged 1 commit into from
May 18, 2016
Merged

ROADMAP: Remove stale targets (landed PRs, image-spec, ocitools, etc.) #435

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
48 changes: 0 additions & 48 deletions ROADMAP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,26 +10,6 @@ Listed topics may defer to the [project wiki](https://github.com/opencontainers/

## 1.0

### Digest and Hashing

A bundle is designed to be moved between hosts.
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.

*Owner:* philips

### Define Container Lifecycle

Containers have a lifecycle and being able to identify and document the lifecycle of a container is very helpful for implementations of the spec.
The lifecycle events of a container also help identify areas to implement hooks that are portable across various implementations and platforms.

*Owner:* mrunalp

### Define Standard Container Actions (Target release: v0.3.0)

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.

*Owner:* duglin

### Container Definition

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

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

### Validation Tooling (Target release: v0.3.0)

Provide validation tooling for compliance with OCI spec and runtime environment.

*Owner:* mrunalp

### Testing Framework

Provide a testing framework for compliance with OCI spec and runtime environment.

*Owner:* liangchenye

### Version Schema

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

*Owner:* vbatts

### Printable/Compiled Spec

Regardless of how the spec is written, ensure that it is easy to read and follow for first time users.

Part of this is resolved. Produces an html & pdf.
Done
Would be nice to publish to the OCI web site as part of our release process.

*Owner:* vbatts

### Base Config Compatibility

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

*Owner:*

### Distributable Format

A common format for serializing and distributing bundles.

*Owner:* vbatts