Rickard Öberg wrote:
Georg Ragaller wrote:
With a linear history this might be enough, but consider this history:
1.0 -> 1.1 -> 1.2
| ^
---> 1.0.1 -|
1.0 -> 1.1 adds property X
1.0 -> 1.0.1 adds properties X and Y
1.1 -> 1.2 adds Y
1.0.1 -> 1.2 adds nothing
how should the 'toVersion("1.2")' rule then look like?
I've never seen non-linear version histories, especially not when it
comes to state in domain models. Even in the above case you really
would be upgrading 1.0->1.0.1->1.1->1.2, which makes the branch not
really different from the main.
But what is the reason 1.1 does not have Y? Are you saying that 1.0.1
has a feature Y that is then not available in 1.1, and is readded for
1.2? That sounds weird...
I've seen them and see them, but only for customer releases. So probably
the version numbers if choosen are irritating.
Cheers
Georg
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
