ROADMAP.md

CNCF CI Roadmap (cncf.ci)

Work in Progress

This document defines a high level roadmap for cncf.ci 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 and issue-for-issue plans.

The roadmap below outlines new features that will be added to cncf.ci, and while subject to change, define the features that future versions will include.

CNCF CI Roadmap (cncf.ci)

Date	Milestone	Features	Events
January 2019	n/a	Announce plan and design for cncf.ci v2.0	CI Working group
February 2019	v2.0	Release cncf.ci v2.0.0	CI Working group
March 2019	v2.1	Support managing project details from per project repositories	ONS NA (April 3-5)
April 2019	v2.2	Add K8s version selector dropdown to Test Environment	CI Working group
April 2019	v2.3	Add K8s Arm support to Test Environment	CI Working group
May 2019	v2.4	Add Arm support to CoreDNS, Prometheus, Fluentd, Intro & Deep Dive on cncf.ci	KubeCon EU (May 20-23)
June 2019	v2.4.1	Add Arm support to Envoy, CI Refactor/Kubespray	KubeCon China 2019
July 2019	v2.5	Add support for external contributions to cncf.ci, Add project-type headers and alpha sorting, CI Refactor/Kubespray	CI Working group
August 2019	v2.6	Add Linkerd 2.x, Create an external Plugin for Travis CI, CI Refactor/Kubespray	CI Working group
September 2019	v3.0	CI Refactor/Add Kubespray to CI system, Update K8s Stable release, Disable cross-cloud, Add containerd support, Add radio button controls, Software updates	ONS EU (Sept 23-25)
October 2019	v3.1	Add Jaeger (using Travis CI integration), Add containerd name and icon to Test Environment UI, Documentation - Adding projects to cncf.ci	CI Working Group
November 2019	v3.2	Add Vitess (using Travis CI integration), Create GitHub Actions CI integration, Intro & Deep Dive on cncf.ci, Plan integration with external artifacts for deploy status on cncf.ci	KubeCon NA (Nov 18-21)
December 2019	v3.3	Add etcd (using Travis CI integration), Start adding deploy status for Linkerd 2.x, Jaeger or Vitess, Start saving history to add stateful URLs to share test results per Test Environment configuration	[TBD]