+Event versions
+==============
+
+The following table lists the data-updated-event schema evolution over releases :
+
+ +-----------+------------+-------------------------+---------------------+
+ | Version | Release | Compatibility Type | Upgrade First |
+ | | | (with previous version) | |
+ +===========+============+=========================+=====================+
+ | v1 | Istanbul | n/a | Any order |
+ +-----------+------------+-------------------------+---------------------+
+ | v2 | Jakarta | Backward | Consumer (Temporal) |
+ +-----------+------------+-------------------------+---------------------+
+
+**Compatibility Types**
+
+Several compatibility types exist when an event schema definition is evolving from one release to the next one:
+
+- Backward compatibility means that consumers using the new schema can read data produced with the previous schema.
+- Forward compatibility means that data produced with a new schema can be read by consumers using the previous schema.
+- Full compatibility means that schemas are both backward and forward compatible: old data can be read with the new schema, and new data can also be read with the previous schema.
\ No newline at end of file