Skip to content

Latest commit

 

History

History
98 lines (77 loc) · 3.88 KB

ROADMAP.md

File metadata and controls

98 lines (77 loc) · 3.88 KB
Raw

Roadmap

The CloudEvents Roadmap.

Note: The ordered lists for each milestone provide a way to reference each item; they don't imply an order for implementation.

Setup - Completed - 2018/02/26

  1. Establish governance, contributing guidelines and initial stakeholders.
  2. Define design goals for CloudEvents V.1.
  3. Describe the scope of the specification.
  4. Draft educational materials that provide context for reading the spec.

0.1 - Completed - 2018/04/20

  1. Draft specification that project members agree could provide interoperability.
  2. Include an initial set of use-cases for CloudEvents.
  3. Define a type system for CloudEvents values.
  4. Document at least 3 sample events that conform to the specification.
  5. Github repo is organized to be approachable to a engineers who might want to implement the spec.
  6. Finalize logo.
  7. Create and deploy a website that features a simple overview, email list and directs visitors to Github.
  8. Store all website assets in the CloudEvents repository, under the governance of the project.
  9. Have at least 2 implementations of the specification that can demonstrate interoperability.
  10. Include a specification for mapping the CloudEvents specification to HTTP.
  11. Include a specification for mapping the CloudEvents specification to JSON.
  12. Changes to the spec to facilitate adoption.
  13. Publicize at conferences (CloudNativeCon Europe).
  14. Interoperability demo.
    1. At least one open source implementation of sending and receiving events, see community open source.
    2. Events are sent by code written by Developer1 and received by code written by Developer2, where Developer1 has no knowledge of Developer2.

0.2 - Completed - 2018/12/06

  1. Incorporate learnings and feedback from interop demo to support wider adoption.
  2. Draft documentation, developer and/or user guide.
  3. Resolve all known large design issues (excluding security issues).
  4. Resolve all known "proposed required attributes" issues.
  5. Interoperability demo 2
    1. Details to be determined.
    2. Showcase demo at conferences - perhaps KubeCon NA 2018.
  6. Define the set of protocol and serialization mappings we're going to produce for 0.4 milestone.

0.3 - Completed - 2019/06/13

  1. Resolve all known "proposed optional attributes" issues.
  2. Resolve all known "security related" issues.
  3. Review spec for practical-use issues:
    1. Consider context size limits.
    2. Consider restricting character sets of String properties or key names.
    3. Consider defining uniqueness constraints of event id.
    4. Consider which fields will be immutable (prevents annotation or redaction).
    5. Consider validating protocol bindings with load tests.

1.0-rc1 - Completed - 2019/09/19

  1. Complete all issues and PRs tagged as v1.0.
  2. Decide on duration and exit criteria for 'verification & testing' period.

1.0 - Completed - 2019/10/24

  1. Completion of exit criteria for 'verification & testing' period.
  2. Completion of as many try-for-v1.0 issues and PRs as possible. The expectation is that these are non-breaking changes to the core spec. Format and protocol-binding specs may introduce breaking change if necessary to align with the core spec.

1.0.1 - Completed - 2020/12/10

  1. See V1.0.1 Release for details.

1.0.2 - Completed - 2022/02/03

  1. See V1.0.2 Release for details.

Future

  • All remaining issues and PRs will be examined.
  • How, and when, future releases (major, minor or patch) will be released will be determined by based on the set of changes that have been approved.