Page History

...

Question to answer: what constitutes the *range \[1.2,1.3)* and how flexible this implementation should be?
Various options:

1. 1.2, 1.3-SNAPSHOT, 1.3-alpha-1, 1.3-alpha-2, 1.3-beta-1
2. 1.2, 1.3-alpha-1, 1.3-alpha-2, 1.3-beta-1
3. 1.2

All 3 options have use cases behind them, how general those use cases are and should all 3 options be implemented - remains open.

Solution to the above problem - Quality Range

In order to cover all the use cases regarding the upper limit of the version range, I introduced a Quality Range to Mercury. This allows us to configure Version Range to accept

1. QualityRange.ALL
2. is split into two
   1. QualityRange.ALPHA
   2. QualityRAnge.BETA
3. QualityRange.RELEASE

As a result all 3 cases could be configured into Mercury

Everybody seem to agree that plugin versioning should be identical to regular dependency versioning, so the discussion really applies to both.

...