From: Greg Luck <gluck_at_gregluck.com>
Date: Wed, 28 Sep 2016 16:00:56 -0700

Yes an MR is planned. We are following that process and have all the closed issues listed in the new version of the spec doc.

Here is where we are at on the 1.1.0 Specification: https://docs.google.com/document/d/14BvLUyv5U3zhsbIGwA4hkLfFieBkaCPfaHazh_yQGSY/edit?usp=sharing

And at the very end in the Appendix is the change log. This is what we have so far:

Maintenance Release 1.1 Specification

https://github.com/jsr107/jsr107spec/issues/308 <https://github.com/jsr107/jsr107spec/issues/308> Wrong version in Spec License. Changed to 1.1
https://github.com/jsr107/jsr107spec/issues/333 <https://github.com/jsr107/jsr107spec/issues/333> Relicensed the Spec API under CDDL1.1 and GPLv2 with Classpath exception. We had wrongly used the JPA license for the API in the 1.0 release.
https://github.com/jsr107/jsr107spec/issues/342 <https://github.com/jsr107/jsr107spec/issues/342> Added clarifications from the spec to the JavaDoc.
https://github.com/jsr107/jsr107spec/issues/334 <https://github.com/jsr107/jsr107spec/issues/334> Attempting to remove on the iterator of CacheNames does not throw an IllegalStateException, but rather an UnsupportedOperationException.
https://github.com/jsr107/jsr107spec/issues/335 <https://github.com/jsr107/jsr107spec/issues/335> Clarified Entry Processor Example 3
https://github.com/jsr107/jsr107spec/issues/336 <https://github.com/jsr107/jsr107spec/issues/336> EntryProcessor MutableEntry.remove() listener effect clarification
https://github.com/jsr107/jsr107spec/issues/337 <https://github.com/jsr107/jsr107spec/issues/337> Clarified Iterator and removed reference to non-existent read listener.
https://github.com/jsr107/jsr107spec/issues/363 <https://github.com/jsr107/jsr107spec/issues/363> Changed Yes (when the key is associated with an existing value) as the result CacheWriter result for getAndReplace.
https://github.com/jsr107/jsr107spec/issues/320 <https://github.com/jsr107/jsr107spec/issues/320> CompletionListenerFuture wakeup for multiple threads, protect against spurious wakeup
https://github.com/jsr107/jsr107spec/pull/364 <https://github.com/jsr107/jsr107spec/pull/364> Clarify Duration JavaDoc.



Regards

Greg Luck

web: http://gregluck.com <http://gregluck.com/>
skype: gregrluck
mobile US: +1 650 924 6244
mobile Australia: +61 408 061 622

> On 28 Sep. 2016, at 11:07 am, Bill Shannon <bill.shannon_at_oracle.com> wrote:
>
> Which is fine, but it means the update overall is *not* an "errata".
> It's a new version of the spec that includes both API changes and errata.
> Presumably you'll use the JCP Maintenance Release process for these changes.
>
> Just trying to make sure we're all using consistent terminology.
>
>
> Greg Luck wrote on 09/28/16 10:04 AM:
>> Bill
>>
>> Around 80-90% of the changes are errata, as defined. We have a couple of very
>> minor behaviour changes. No new methods.
>>
>> Regards
>>
>> Greg Luck
>>
>>> On 28 Sep. 2016, at 8:45 am, Bill Shannon <bill.shannon_at_oracle.com
>>> <mailto:bill.shannon_at_oracle.com>> wrote:
>>>
>>> Greg, do you really mean "errata", as described on our JCP processes page [1]?
>>>
>>> An errata does not change the RI or the version number of the API.
>>>
>>> [1] https://java.net/projects/javaee-spec/pages/JCPProcesses
>>>
>>>
>>> gluck_at_gregluck.com <mailto:gluck_at_gregluck.com> wrote on 09/28/2016 08:35 AM:
>>>> JCache 1.1 is an errata release. There is nothing new being added.
>>>>
>>>> See the list of spec issues targeted here -
>>>> https://github.com/jsr107/jsr107spec/issues?utf8=✓&q=is%3Aissue%20miles
>>>> tone%3A1.1
>>>>
>>
>