Add patch version for events

Based on the discussion on the PR and slack, adding the patch version
for events as well.

Signed-off-by: Andrea Frittoli <[email protected]>

Author: afrittoli

continuous-integration-pipeline-events.md

@@ -72,7 +72,7 @@ An `artifact` is usually produced as output of a build process. Events need to b
 
 This event represents a Build task that has been queued; this build process usually is in charge of producing a binary from source code.
 
-- Event Type: __`dev.cdevents.build.queued.0.1-draft`__
+- Event Type: __`dev.cdevents.build.queued.0.1.0-draft`__
 - Predicate: queued
 - Subject: [`build`](#build)
 
@@ -87,7 +87,7 @@ This event represents a Build task that has been queued; this build process usua
 
 This event represents a Build task that has been started; this build process usually is in charge of producing a binary from source code.
 
-- Event Type: __`dev.cdevents.build.started.0.1-draft`__
+- Event Type: __`dev.cdevents.build.started.0.1.0-draft`__
 - Predicate: started
 - Subject: [`build`](#build)
 
@@ -102,7 +102,7 @@ This event represents a Build task that has been started; this build process usu
 
 This event represents a Build task that has finished. This event will eventually contain the finished status, success, error or failure
 
-- Event Type: __`dev.cdevents.build.finished.0.1-draft`__
+- Event Type: __`dev.cdevents.build.finished.0.1.0-draft`__
 - Predicate: finished
 - Subject: [`build`](#build)
 
@@ -118,7 +118,7 @@ This event represents a Build task that has finished. This event will eventually
 
 This event represents a Test task that has been queued, and it is waiting to be started.
 
-- Event Type: __`dev.cdevents.testcase.queued.0.1-draft`__
+- Event Type: __`dev.cdevents.testcase.queued.0.1.0-draft`__
 - Predicate: queued
 - Subject: [`testCase`](#testcase)
 
@@ -133,7 +133,7 @@ This event represents a Test task that has been queued, and it is waiting to be
 
 This event represents a Test task that has started.
 
-- Event Type: __`dev.cdevents.testcase.started.0.1-draft`__
+- Event Type: __`dev.cdevents.testcase.started.0.1.0-draft`__
 - Predicate: started
 - Subject: [`testCase`](#testcase)
 
@@ -148,7 +148,7 @@ This event represents a Test task that has started.
 
 This event represents a Test task that has finished. This event will eventually contain the finished status: success, error or failure.
 
-- Event Type: __`dev.cdevents.testcase.finished.0.1-draft`__
+- Event Type: __`dev.cdevents.testcase.finished.0.1.0-draft`__
 - Predicate: finished
 - Subject: [`testCase`](#testcase)
 
@@ -163,7 +163,7 @@ This event represents a Test task that has finished. This event will eventually
 
 This event represents a Test suite that has been started.
 
-- Event Type: __`dev.cdevents.testsuite.started.0.1-draft`__
+- Event Type: __`dev.cdevents.testsuite.started.0.1.0-draft`__
 - Predicate: started
 - Subject: [`testSuite`](#testsuite)
 
@@ -178,7 +178,7 @@ This event represents a Test suite that has been started.
 
 This event represents a Test suite that has has finished, the event will contain the finished status: success, error or failure.
 
-- Event Type: __`dev.cdevents.testsuite.finished.0.1-draft`__
+- Event Type: __`dev.cdevents.testsuite.finished.0.1.0-draft`__
 - Predicate: finished
 - Subject: [`testSuite`](#testsuite)
 
@@ -193,7 +193,7 @@ This event represents a Test suite that has has finished, the event will contain
 
 The event represents an artifact that has been packaged for distribution; this artifact is now versioned with a fixed version.
 
-- Event Type: __`dev.cdevents.artifact.packaged.0.1-draft`__
+- Event Type: __`dev.cdevents.artifact.packaged.0.1.0-draft`__
 - Predicate: packaged
 - Subject: [`artifact`](#artifact)
 
@@ -206,7 +206,7 @@ The event represents an artifact that has been packaged for distribution; this a
 
 The event represents an artifact that has been published and it can be advertised for others to use.
 
-- Event Type: __`dev.cdevents.artifact.published.0.1-draft`__
+- Event Type: __`dev.cdevents.artifact.published.0.1.0-draft`__
 - Predicate: published
 - Subject: [`artifact`](#artifact)
 

core.md

@@ -66,7 +66,7 @@ Due the dynamic nature of Pipelines, most of actual work needs to be queued to
 happen in a distributed way, hence queued events are added. Adopters can choose
 to ignore these events if they don't apply to their use cases.
 
-- Event Type: __`dev.cdevents.pipelinerun.queued.0.1-draft`__
+- Event Type: __`dev.cdevents.pipelinerun.queued.0.1.0-draft`__
 - Predicate: queued
 - Subject: [`pipelineRun`](#pipelinerun)
 
@@ -81,7 +81,7 @@ to ignore these events if they don't apply to their use cases.
 
 A pipelineRun has started and it is running.
 
-- Event Type: __`dev.cdevents.pipelinerun.started.0.1-draft`__
+- Event Type: __`dev.cdevents.pipelinerun.started.0.1.0-draft`__
 - Predicate: started
 - Subject: [`pipelineRun`](#pipelinerun)
 
@@ -96,7 +96,7 @@ A pipelineRun has started and it is running.
 
 A pipelineRun has finished, successfully or not.
 
-- Event Type: __`dev.cdevents.pipelinerun.finished.0.1-draft`__
+- Event Type: __`dev.cdevents.pipelinerun.finished.0.1.0-draft`__
 - Predicate: finished
 - Subject: [`pipelineRun`](#pipelinerun)
 
@@ -113,7 +113,7 @@ A pipelineRun has finished, successfully or not.
 
 A taskRun has started and it is running.
 
-- Event Type: __`dev.cdevents.taskrun.started.0.1-draft`__
+- Event Type: __`dev.cdevents.taskrun.started.0.1.0-draft`__
 - Predicate: started
 - Subject: [`taskRun`](#taskrun)
 
@@ -129,7 +129,7 @@ A taskRun has started and it is running.
 
 A taskRun has finished, successfully or not.
 
-- Event Type: __`dev.cdevents.taskrun.finished.0.1-draft`__
+- Event Type: __`dev.cdevents.taskrun.finished.0.1.0-draft`__
 - Predicate: finished
 - Subject: [`taskRun`](#taskrun)
 

primer.md

@@ -100,52 +100,62 @@ extensions](https://github.com/cloudevents/spec/blob/v1.0.1/documented-extension
 
 ## Versioning
 
-The CDEvents specification and events are versioned independently, both following the
-principle of semantic versioning.
+The CDEvents specification and events are versioned independently, both
+following the principle of semantic versioning.
 
 ### Versioning of CDEvents
 
-Individual CDEvents are versioned using semantic versioning, with a `major.minor`
-format of the version.
+Individual CDEvents are versioned using semantic versioning, with a
+`major.minor.patch` format of the version.
 
-- Backward compatible changes to events are identified by a change in the minor
-  version of the event, for instance 0.1 -> 0.2. This means that an unmodified
-  consumer can parse a more recent minor version of an event, as long as it ignores
-  extra fields. Fields introduced in the new minor version will be ignored, but
-  everything else will work as before.
+Backward compatible changes are changes that allow existing consumers to parse
+messages with a newer version, have access to the same data as before, as long
+the extra fields are ignored. Broadening the accepted values for a property is a
+backward incompatible change, as the consumer may not be prepared to manage the
+new format of value.
 
-- Backward incompatible changes to events are identified by a change in the major
-  version of the event, for instance 0.3 -> 1.0. Moved or removed fields will
-  require a new major version.
+Note that this means that consumers SHOULD be prepared to handle (and disregard)
+unrecognized properties in higher minor versions than they are familiar with.
 
-while the specification of an event is work in progress, its version is tagged with
-an extra `-draft` at the end.
+- Major versions (e.g. 0.3.1 -> 1.0.0): backward incompatible changes to events.
+  Renamed, moved or removed fields requires a new major version.
 
-The version of an event is included in its type. This allows for easy filtering of
-events of a specific version, by looking at a single field in the context. Examples
-of full event versions are:
+- Minor versions (e.g. 0.1.2 -> 0.2.0): backward compatible changes to events
+  that involve a structural change in the schema. A new field is added, a copy
+  of an existing field is added and the old location deprecated, or a new
 
-- `dev.cdevents.build.queued.0.1-draft`
-- `dev.cdevents.environment.deleted.0.1`
+- Patch versions (e.g. 0.1.0 -> 0.1.1): backward compatible changes to events
+  that do not involve any structural change in the schema, for instance
+  narrowing the accepted values for a property
+
+While the specification of an event is work in progress, its version is tagged
+with an extra `-draft` at the end.
+
+The version of an event is included in its type. This allows for easy filtering
+of events of a specific version, by looking at a single field in the context.
+Examples of full event versions are:
+
+- `dev.cdevents.build.queued.0.1.0-draft`
+- `dev.cdevents.environment.deleted.0.1.0`
 
 ### Versioning of the CDEvents specification
 
-The overall CDEvents specification is versioned using semantic versioning, with a
-`major.minor.patch` format of the version. The specification version is associated
-to a git version (tag) in the `cdevents/spec` repository, in the format
-`vMajor.Minor.Patch`.
+The overall CDEvents specification is versioned using semantic versioning, with
+a `major.minor.patch` format of the version. The specification version is
+associated to a git version (tag) in the `cdevents/spec` repository, in the
+format `vMajor.Minor.Patch`.
 
-- A specification that includes only cosmetic fixes is identified by a change in the
-  patch version, for instance 0.1.0 -> 0.1.1
+- A specification that includes only cosmetic fixes is identified by a change in
+  the patch version, for instance 0.1.0 -> 0.1.1
 
-- A specification that includes only backwards compatible change is identified by
-  a change in the minor version, for instance 0.1.3 -> 0.2.0
+- A specification that includes only backwards compatible change is identified
+  by a change in the minor version, for instance 0.1.3 -> 0.2.0
 
 - A specification that includes at least one backward incompatible change, is
   identified by a change in the major version, for instance 0.1.2 -> 2.0.0
 
-While a version of the specification is work in progress, its version is tagged with
-an extra `-draft` at the end, for instance 0.1.0-draft.
+While a version of the specification is work in progress, its version is tagged
+with an extra `-draft` at the end, for instance 0.1.0-draft.
 
 ### Development of a new version
 

source-code-version-control.md

@@ -61,7 +61,7 @@ A `change` identifies a proposed set of changes to the content of a `repository`
 
 A new Source Code Repository was created to host source code for a project.
 
-- Event Type: __`dev.cdevents.repository.created.0.1-draft`__
+- Event Type: __`dev.cdevents.repository.created.0.1.0-draft`__
 - Predicate: created
 - Subject: [`repository`](#repository)
 
@@ -78,7 +78,7 @@ A new Source Code Repository was created to host source code for a project.
 
 A Source Code Repository modified some of its attributes, like location, or owner.
 
-- Event Type: __`dev.cdevents.repository.modified.0.1-draft`__
+- Event Type: __`dev.cdevents.repository.modified.0.1.0-draft`__
 - Predicate: modified
 - Subject: [`repository`](#repository)
 
@@ -93,7 +93,7 @@ A Source Code Repository modified some of its attributes, like location, or owne
 
 ### `repository deleted`
 
-- Event Type: __`dev.cdevents.repository.deleted.0.1-draft`__
+- Event Type: __`dev.cdevents.repository.deleted.0.1.0-draft`__
 - Predicate: modified
 - Subject: [`repository`](#repository)
 
@@ -110,7 +110,7 @@ A Source Code Repository modified some of its attributes, like location, or owne
 
 A branch inside the Repository was created.
 
-- Event Type: __`dev.cdevents.branch.created.0.1-draft`__
+- Event Type: __`dev.cdevents.branch.created.0.1.0-draft`__
 - Predicate: created
 - Subject: [`branch`](#branch)
 
@@ -125,7 +125,7 @@ A branch inside the Repository was created.
 
 A branch inside the Repository was deleted.
 
-- Event Type: __`dev.cdevents.branch.deleted.0.1-draft`__
+- Event Type: __`dev.cdevents.branch.deleted.0.1.0-draft`__
 - Predicate: deleted
 - Subject: [`branch`](#branch)
 
@@ -140,7 +140,7 @@ A branch inside the Repository was deleted.
 
 A source code change was created and submitted to a repository specific branch. Examples: PullRequest sent to Github, MergeRequest sent to Gitlab, Change created in Gerrit.
 
-- Event Type: __`dev.cdevents.change.created.0.1-draft`__
+- Event Type: __`dev.cdevents.change.created.0.1.0-draft`__
 - Predicate: created
 - Subject: [`change`](#change)
 
@@ -155,7 +155,7 @@ A source code change was created and submitted to a repository specific branch.
 
 Someone (user) or an automated system submitted an review to the source code change. A user or an automated system needs to be in charge of understanding how many approvals/rejections are needed for this change to be merged or rejected. The review event needs to include if the change is approved by the reviewer, more changes are needed or if the change is rejected.
 
-- Event Type: __`dev.cdevents.change.reviewed.0.1-draft`__
+- Event Type: __`dev.cdevents.change.reviewed.0.1.0-draft`__
 - Predicate: reviewed
 - Subject: [`change`](#change)
 
@@ -170,7 +170,7 @@ Someone (user) or an automated system submitted an review to the source code cha
 
 A change is merged to the target branch where it was submitted.
 
-- Event Type: __`dev.cdevents.change.merged.0.1-draft`__
+- Event Type: __`dev.cdevents.change.merged.0.1.0-draft`__
 - Predicate: merged
 - Subject: [`change`](#change)
 
@@ -185,7 +185,7 @@ A change is merged to the target branch where it was submitted.
 
 A tool or a user decides that the change has been inactive for a while and it can be considered abandoned.
 
-- Event Type: __`dev.cdevents.change.abandoned.0.1-draft`__
+- Event Type: __`dev.cdevents.change.abandoned.0.1.0-draft`__
 - Predicate: abandoned
 - Subject: [`change`](#change)
 
@@ -200,7 +200,7 @@ A tool or a user decides that the change has been inactive for a while and it ca
 
 A Change has been updated, for example a new commit is added or removed from an existing Change.
 
-- Event Type: __`dev.cdevents.change.updated.0.1-draft`__
+- Event Type: __`dev.cdevents.change.updated.0.1.0-draft`__
 - Predicate: updated
 - Subject: [`change`](#change)