Hello Olingo Dev Community, I want to follow up on the proposal for the versioning schema of Olingo libraries.
I did not get any reply to my last mail, but there was (is) a discussion on GitHub (see e.g. my comment https://github.com/apache/olingo-odata4/pull/130#issuecomment-1732476542). For me, it looks like there is an agreement to change to Semantic Versioning (https://semver.org)with the not backward-compatible releases (V2/V4). As a result, the version of the V2 upgrade release is 3.0.0, and of the V4 upgrade it is 5.0.0 If there is no objection here till the end of October, I follow the Lazy Consensus (https://www.apache.org/foundation/glossary.html#LazyConsensus) and continue as proposed. Btw. I brought this up here again, as the projects mailing list is still the leading decision-making channel (just in case someone is wondering why not just continue in the GitHub PR and take the decision there). However, I’m open to opinions and discussions. Kind Regards, Michael 'mibo' Am 16. Sept. 2023, 10:48 +0200 schrieb mibo <m...@apache.org>: > Hello Dev Community, > > First I want to apologize for the delay with the release and the support for > newer Java / Spring Boot versions. > The reason was that I was very involved in my private and professional life. > I hope I will be better in the next few months. > > The roadmap for Apache Olingo is to do maintenance releases for V2 and V4 by > the end of September and afterward prepare the upgrade releases to support > newer Java / Spring Boot versions. > > The maintenance release for V2 has already started and for V4 I plan to start > preparations next week. > > For the upgrade release, I plan to start preparations beginning / mid of > October and finish it in November. > But before I want to discuss the version schema for both (V2 and V4) Olingo > libraries. > In Olingo we have a bit strange versioning schema because we decided to start > the version of the V2 library with '2' and of the V4 library with '4'. But > today I think this was not so good. > Today I propose to use Semantic Versioning (https://semver.org). starting > with the planned update releases. > Because both releases (V2/V4) are not backward compatible and hence justify > the increase of the major version. > As a result, the version of the V2 upgrade release is 3.0.0, and of the V4 > upgrade it is 5.0.0 > > Before doing this I'm open for feedback from you as the community. > > Kind Regards, Michael
