Proposed updates to Java product versioning policy
Cantor, Scott
cantor.2 at osu.edu
Mon Jun 1 09:54:06 EDT 2015
On 6/1/15, 6:35 AM, "dev on behalf of Ian Young" <dev-bounces at shibboleth.net on behalf of ian at iay.org.uk> wrote:
>The thing that has always irked me most about the general model is indeed the third party library stability part. I think adding the rationale for that is a big help, even if I still feel that to some extent we're playing things more cautiously than we need to in some cases (e.g., Spring patch releases).
As I said, I'm simply articulating what we've done, but that doesn't mean we have to keep doing it.
But we also can't say "plugins will work across minor versions" if we change that.
> I'd suggest adding a reference to the third party library section from the second bullet in the Patch Version Compatibility section. It may also be worth thinking about whether we might make exceptions for some projects that have taken the semantic versioning pledge, although I can see that might be hard to explain.
I think I meant to imply that by saying that we're trying to apply the same API policy to those projects as our own to the extent we can, but I'll review it.
-- Scott
More information about the dev
mailing list