On the other hand, dropped support for no longer supported Java versions is not an API change...
Obter o BlueMail para Android Em 11 de set de 2019 23:28, em 23:28, Mark Murphy <jmarkmur...@gmail.com> escreveu: >Following semantic versioning, might that be considered a serious >enough >breaking change to warrant a 4.0.0? > >Given a version number MAJOR.MINOR.PATCH, increment the: > > 1. MAJOR version when you make incompatible API changes, > 2. MINOR version when you add functionality in a backwards compatible > manner, and > 3. PATCH version when you make backwards compatible bug fixes. > >Additional labels for pre-release and build metadata are available as >extensions to the MAJOR.MINOR.PATCH format. > >I suggest that 4.0.0 is warranted, even if we aren't adding new >functionality. > >On Wed, Sep 11, 2019 at 3:31 PM PJ Fanning ><fannin...@yahoo.com.invalid> >wrote: > >> It's been 6 months since we released XMLBeans 3.1.1. >> The reason I suggest naming next version as 3.2.0 is because we have >> dropped support for Java 6 & 7. >> >> >https://issues.apache.org/jira/browse/XMLBEANS-542?jql=project%20%3D%20XMLBEANS%20AND%20fixVersion%20%3D%20%22Version%203.1.1%22 >> >> >> A few people on stackoverflow have run into >> https://issues.apache.org/jira/browse/XMLBEANS-542 (not that that is >the >> only issue with trying to use POI/XMLBeans on Android. >> >>
