Hi. In general proposal looks good to me, but I agree with Andrey that
sticking to same *major.minor* is too much.
From my perspective using same major is enough. It still will make it
easier to understand correlation between spring
and corresponding extension module, meanwhile preserving enough
If we talk about semver(https://semver.org/)
You have the PATCH version for bug fixes.
But I agree, that we may want to make some improvement on the same Spring
version, and then the PATCH version won't be suitable.
If we keep major only, then my suggestion is not very useful(it will be
harder to
>
> 5. New versioning approach. Use the same major and minor for spring
>extension as the corresponding spring module is used.
What if we need to fix some bug in the module without changing the
corresponding spring module version? I would prefer independent versioning
from spring, but it is f
