884daf3079
The documentation about OCI and appc created uncertainty for users, as shown by the issues #3777 and #3745. This is an attempt to clarify that although not much development is happening in appc, rkt will not drop the ACI support. Once this PR is merged, I would like to delete the project https://github.com/rkt/rkt/projects/5 as it does not contain anything and we have https://github.com/rkt/rkt/projects/4 to track the progress of OCI native support. Fixes https://github.com/rkt/rkt/issues/3777 Fixes https://github.com/rkt/rkt/issues/3745
1.1 KiB
rkt roadmap
This document defines a high level roadmap for rkt development. The dates below should not be considered authoritative, but rather indicative of the projected timeline of the project. The milestones defined in GitHub represent the most up-to-date state of affairs.
rkt's version 1.0 release marks the command line user interface and on-disk data structures as stable and reliable for external development.
Ongoing projects
Kubernetes CRI
Adapting rkt to offer first-class implementation of the Kubernetes Container Runtime Interface.
OCI native support
Supporting OCI specs natively in rkt. Following OCI evolution and stabilization, it will become the preferred way over appc. However, rkt will continue to support the ACI image format and distribution mechanism. There is currently no plans to remove that support from rkt.
Upcoming
Future tasks without a specific timeline are tracked at https://github.com/rkt/rkt/milestone/30.