How best to express version bounds? about modules.dropwizard.io

[joschi]

@jklukas Thanks for bringing this up.

There is no "official" way for expressing the version bounds of one of the listed 3rd party modules.

I guess listing the supported versions is fine ("0.8, 0.9, 1.0").

The reason I dislike open-ended version specifications ("0.7+") is that people would expect things to work with the latest stable version of Dropwizard even if the author(s) didn't test the compatibility.

[jklukas]

I might take a stab at a PR that adds some explicit instruction around this, in particular calling out that package maintainers will need to test on the new versions and update the listing here as new versions are released.

I would imagine we'd want to organize the packages based on most recent verified version. So a bundle that runs on 0.8, 0.9, and 1.0 would be listed with the 1.0 packages.

[ahus1]

@joschi / @jklukas - It seems that can now be closed as the PR is merged?

[jklukas]

Indeed. Closing.