Skip to content

[docs] chore(breaking-changes): add 2.2.0 breaking changes#256

Open
RomuDeuxfois wants to merge 4 commits intomainfrom
issue/255
Open

[docs] chore(breaking-changes): add 2.2.0 breaking changes#256
RomuDeuxfois wants to merge 4 commits intomainfrom
issue/255

Conversation

@RomuDeuxfois
Copy link
Member


## Description of changes

Starting from **OpenAEV 2.2.0**, the interconnection between **OCTI** and **OpenAEV** is only supported with **OCTI 7.0**.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually it's starting from OCTI 7.0 you need OpenAEV 2.2.0
but with an OCTI < 7.0 you can use openaev 2.2.0 or even the 2.1.9

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I made the changes

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • don't use OCTI acronym in documention or product itself -> OpenCTI
  • there is no OpenCTI 7.0 :) you can just say OpenCTI v7

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another point: I hear in discussions that we would like to restore backwards compatibility (new OAEV with old OCTI). I would use a wording that specifically addresses the breakage with OAEV 2.2.0, so removing mentions that suggest a continuity of the breakage in further OAEV versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants