[ 
https://issues.apache.org/jira/browse/IGNITE-27182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Chugunov updated IGNITE-27182:
-------------------------------------
    Epic Link: IGNITE-25883

> Provide compatibility version matrix for rolling upgrade
> --------------------------------------------------------
>
>                 Key: IGNITE-27182
>                 URL: https://issues.apache.org/jira/browse/IGNITE-27182
>             Project: Ignite
>          Issue Type: New Feature
>            Reporter: Aleksandr Chesnokov
>            Assignee: Aleksandr Chesnokov
>            Priority: Major
>              Labels: IEP-132, ise
>
> We currently support only two migration patterns:
>  * X.Y.Z → X.Y.(Z+1)
>  * X.Y.Z → X.(Y+1).0
> These rules are too restrictive. They limit how users can upgrade and create 
> obstacles for forks that introduce their own versioning schemes.
> {*}Proposal{*}: introduce an admin-managed compatibility matrix.
> This matrix defines which source and target versions are compatible. Forks 
> will be able to define their own version formats and simply register 
> compatibility versions
> Admins would be able to add, edit, or remove compatibility rules, enabling a 
> fully customizable upgrade model



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to