Bug 61967 - Semantic Versioning semver
Summary: Semantic Versioning semver
Alias: None
Product: POI
Classification: Unclassified
Component: POI Overall (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal (vote)
Target Milestone: ---
Assignee: POI Developers List
Depends on:
Reported: 2018-01-05 13:57 UTC by Stefan Wendelmann
Modified: 2018-01-07 20:45 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Wendelmann 2018-01-05 13:57:25 UTC
I just updated POI in my Project from 3.5 to 3.17 and got tons of Errors in my Code.

Is it possible to go for a Semantic Versioning so one could see if the API changes and is not compatible with the old one anymore?

IMHO the best approach is https://semver.org/

Best regards

Stefan Wendelmann
Comment 1 PJ Fanning 2018-01-05 15:26:29 UTC
The next release is 4.0.0 and we will be using semver.
The policy in the past is that APIs deprecated for the 1st time in say, 3.5, could be removed in 3.7 or afterwards - ie that they would be retained for 2 releases.
Comment 2 Nick Burch 2018-01-07 20:45:20 UTC
You just jumped 8.5 years, so I'm not sure that any amount of SEMVER is going to help there! IIRC you also jumped from well well before SEMVER was invented... Please see the changelog from http://poi.apache.org/changes.html#3.5-final onwards for the main changes made, but as PJ Fanning said, you generally need to jump 1-2 versions at a time (not 12!) and fix the deprecations as you go