[cross-project-issues-dev] EPL 2.0 upgrade => minor or major version cha

[Karsten Thoms <karsten.thoms@xxxxxxxxx>]

In EPL 2.0 FAQ [1] it is mentioned that

   "Users and adopters of Eclipse projects should expect the next simultaneous release of each Eclipse project will be using EPL-2.0.“

For such an Eclipse project migrating to EPL 2.0, does this imply a major version change? Or is a minor version change enough? The versioning guidelines [2] state that the minor version is to be changed

   "when a plug-in changes in an "externally visible“ way"

Could an Eclipse project change to EPL 2.0 with a minor release then, since the license upgrade is just an „externally visible“ change?

Kind regards,

~Karsten

[1] https://www.eclipse.org/legal/epl-2.0/faq.php#h.60mjudroo8e5

[2] https://wiki.eclipse.org/Version_Numbering#When_to_change_the_minor_segment