Hi, On Tue, Feb 28, 2017 at 5:45 PM, Stefan Seifert <[email protected]> wrote: > ...the drawback of this proposal is that we have a few older releases in the > 1.x > line (1.2.0 and 1.2.2) that are not in line with semantic versioning, but > this would be > fixed in 1.3.0 and upwards...
I think that's reasonable. The alternative would be to use 3.0.0 for the "legacy branch" to more clearly indicate the fork, but that's not necessarily better. How do you intend to manage both branches of the fork? svn branches? Maybe creating a new "legacy" Maven module for one of them would be clearer. -Bertrand
