That wording is strange. I don't think that "simultaneous" should be there. I'll sort that out.
IMHO, semantic versioning is tied to the technical implementation. You can update the project license whenever you're ready and include notification of that as a feature of your next major/minor/service release. I don't subscribe to platform-dev (heresy... I know), so please pass this response to them on my behalf. HTH, Wayne On Mon, Feb 26, 2018 at 10:44 AM, Karsten Thoms <[email protected]> wrote: > 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 > > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > -- Wayne Beaton Director of Open Source Projects The Eclipse Foundation
_______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
