Hey Jochen,

Thanks for the info. I get wanting to make it easy to determine which 
module versions are compatible with which versions of Dropwizard, but maybe 
there's a middle ground between the two approaches?

I don't really see *a ton of value *being added by matching all the way 
down to the patch version. Maybe instead, the module versions match the 
major and minor version of Dropwizard they're compatible with, and then 
beyond that we offer some sort of semantic versioning info for the rest of 
the version number.
For example, and maybe this is too complicated without additional docs, but 
something like: <DW Major Version>.<DW Minor Version>.<Module Major 
Version>.<Module Minor Version>.<Module Patch Version> or *1.3.1.2.5*. 

Otherwise, yeah there are some downsides with the Spring approach you 
mention, but *in theory*, if a compatibility matrix were added to the 
README and updated alongside the module/Dropwizard versions, would that 
address those concerns sufficiently? 

On Wednesday, June 12, 2019 at 1:07:00 PM UTC-7, Jochen Schalanda wrote:
>
> Hi Michael, 
>
> > The main drawbacks with switching to this are: 
> > 1. We'd lose consistency with all of the other Dropwizard module 
> projects, unless they also changed their versioning strategy. 
> > 2. We'd likely want to maintain a version compatibility matrix in each 
> module's README. 
>
> The idea with the current versioning strategy for (official) Dropwizard 
> modules was to make it very easy for users to see, which version of 
> Dropwizard they were targeting. 
>
> This of course comes at the cost of not being able to use semantic 
> versioning with the modules themselves, but we thought it might be worth 
> it, especially since we wanted to maintain modules for more than one 
> major/minor version of Dropwizard. 
>
> The Spring ecosystem is doing it a little differently and is using 
> semantic versioning (more or less) for all sub-projects on their own. This 
> leads, in my humble opinion, to some confusion which versions of Spring 
> Security and Spring Cloud work well with a specific version of Spring Boot. 
> YMMV. ;-) 
>
>
> Cheers, 
> Jochen 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"dropwizard-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dropwizard-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dropwizard-dev/6454bd57-4dd5-4f28-871b-cc8a2d6cb7bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to