Hi, I am having this question for another project I am working on and since it (obviously) uses Maven, I wonder if I could collect some feedback over here. It's halfway between user and dev. Apologizes if I sent to the wrong list :)
Assume a projet providing a library utility over a framework (here Vaadin). The current stable version of Vaadin is 6.7.x and the team is working on the upcoming 7 version. This version is not stable at all and has a number of backward incompatible changes that require a separate branch for it (some core concepts have slightly moved, the api has changed, etc). On master, I have a 0.3 release using Vaadin 6.7.6 (stable release). I want to start a branch to make all the necessary changes to use Vaadin 7 but how do I version it? Some ideas: * 0.3 is Vaadin 6-based, 0.4 is Vaadin 7-based, 0.5 is Vaadin6-based, etc.: It's weird because the features of the library should be exactly the same (the only difference is the underlying API that is being used) * 0.3 became 1.0 and the Vaadin-7 based version is 2.0-SNAPSHOT: not sure it represents the reality because the library itself will not change much. Again, same features, slightly different API * We use a different version number (something like 0.4-v6 for the Vaadin 6 branch and 0.4-v7 for the Vaadin 7 branch). And eventually, the Vaadin-6 based version would go in maintenance mode and we would only keep the Vaadin-7 based one for further improvements. The last option seems to be the best I have so far for my needs but it does not sound it complies with the version naming scheme best practice. Any idea? Thanks, S.
