Proposed updates to Java product versioning policy

[Daniel Fisher]

On Fri, May 29, 2015 at 2:02 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> I had an action from a few dev calls back to update the Java versioning
> policy page [1] with new text covering more of the edge cases and questions
> that keep coming up on the calls.
>
> I've finally done so and marked it as a draft (I did it as one edit, so
> the previous page version should have the old policy if we want it back for
> some reason).
>
> Please review and raise any concerns on the list, or identify anything you
> still think is overlooked.
>
> Of course, if you think we should abandon the "compatibility over
> everything" model that this is maintaining, that's fine. I wasn't intending
> to change the policy, just clarify it and extend it to cover the questions.
>

Can something like this be added:

"3rd party libraries that add or remove APIs that we believe are out of
scope for our product or unlikely to be used by developers may be updated
in a minor release."

I think that is the essence of what I heard on the call.

--Daniel Fisher
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20150601/6b8d4b97/attachment.html>