versioning scheme and breaking changes

Hi,

Would be great if you could change the current versioning scheme to respect the most used [semantic versionning](versioning ):

> Summary
> Given a version number MAJOR.MINOR.PATCH, increment the:
>
> MAJOR version when you make incompatible API changes,
> MINOR version when you add functionality in a backwards compatible manner, and
> PATCH version when you make backwards compatible bug fixes.

It's a pain every time we update our dependencies, we have to remember that assertj has breaking changes even though only minor version were updated.

By the way, we're stuck on version 3.17 because of this change:

> Breaking change: disable bare name getter by default, to get the previous behaviour back, call Assertions.setExtractBareNamePropertyMethods(true);

What's the simplest way to get the previous behaviour? Adding this line in every test?

Regards

Empieza revisando el proceso actual de versionado y lanzamiento del proyecto; después, examina el breaking change descrito para la versión 3.17. Se considera terminado cuando el proyecto sigue el versionado semántico para cambios incompatibles, compatibles y correcciones de errores, con una ruta de migración clara para restaurar el comportamiento anterior.

Escrito por el modelo de indexación a partir del texto del issue.