Fwd: JSR 243 Maintenance Review 5

[Craig Russell <ap...@gmail.com>]

> Begin forwarded message:
> 
> From: Harold Ogle <ha...@oracle.com>
> Subject: Re: JSR 243 Maintenance Review 5
> Date: February 3, 2022 at 10:31:06 AM PST
> To: Craig Russell <ap...@gmail.com>
> 
> Craig:
> 
> Congratulations on passing the Maintenance Review ballot! I hope that you and your circle of family and friends are all in good health and spirits.
> 
> I wanted to check in with you. Now that you've completed the Maintenance Review, the next step in Maintenance Release. When will you provide the materials for the Maintenance Release to spec-submit@jcp.org <ma...@jcp.org>? These are listed online, but are here for your convenience:
> 
> The revised final Specification, in pdf or zip format (be aware that Javadoc files must be zipped).
> The URL of the publicly accessible Reference Implementation (or publicly accessible instructions on how to access the RI)
> The URL of the publicly accessible Technology Compatibility Kit (or publicly accessible instructions on how to access the TCK)
> the answer to the following questions, provided separately for each specification file you provide for posting:
> A. Does the file include software codes in the following format:
> Binary : Yes ______  No ______
> Source (compilable) : Yes _____  No _____
> Javadocs : Yes _____  No _____
> B. Do the codes or the file call on, contain, use, or demonstrate encryption technology?
> Yes _____  No _____
> If yes, please describe in detail.
> The PMO will use your answers to update the Export Classification Control Number (ECCN) with the US State Department for the posting of the Maintenance Release specification.
> 
> The version number of the specific specification document you are submitting, the anticipated release date, and the full corporate name and address of the Spec Lead Member(s). This will be used in the final specification license.
> The name and contact information for the Maintenance Lead(s)
> The URL of the updated Issue List
> An Answer to the question: Do you intend to continue developing this Specification through Maintenance Reviews or a follow-on JSR?
> 
>      Thank you,
> 
>          Harold
> JCP Program Management Office
> 
> On 12/9/2021 10:57 AM, Craig Russell wrote:
>> 
>> Please consider this request for Maintenance Review 5 of JSR-243, Java Data Objects (JDO).
>> 
>> The maintenance of JDO is done in public on the mail list jdo-dev:https://urldefense.com/v3/__https://lists.apache.org/list.html?jdo-dev@db.apache.org__;!!ACWV5N9M2RV99hQ!enxjr_gVpOmo6geh-OR88IUeabvLgDUAr-7j6ibA3Yb_Y5qVqnkJVwCvnsdIajDh$ <https://urldefense.com/v3/__https://lists.apache.org/list.html?jdo-dev@db.apache.org__;!!ACWV5N9M2RV99hQ!enxjr_gVpOmo6geh-OR88IUeabvLgDUAr-7j6ibA3Yb_Y5qVqnkJVwCvnsdIajDh$> 
>> 
>> The issues are tracked via JIRA. These are the issues being proposed for Maintenance Review 5: 
>> https://urldefense.com/v3/__https://issues.apache.org/jira/browse/JDO-795?jql=project*20*3D*20JDO*20AND*20fixVersion*20*3D*20*22JDO*203.2*22__;JSUlJSUlJSUlJSU!!ACWV5N9M2RV99hQ!enxjr_gVpOmo6geh-OR88IUeabvLgDUAr-7j6ibA3Yb_Y5qVqnkJVwCvnvBWvzSy$ <https://urldefense.com/v3/__https://issues.apache.org/jira/browse/JDO-795?jql=project*20*3D*20JDO*20AND*20fixVersion*20*3D*20*22JDO*203.2*22__;JSUlJSUlJSUlJSU!!ACWV5N9M2RV99hQ!enxjr_gVpOmo6geh-OR88IUeabvLgDUAr-7j6ibA3Yb_Y5qVqnkJVwCvnvBWvzSy$> 
>> 
>> The changes are summarized here [1]
>> 
>> The proposed updated specification is here [2]
>> 
>> The license for the TCK, and RI are the Apache License, v2.0: 
>> https://urldefense.com/v3/__https://www.apache.org/licenses/LICENSE-2.0__;!!ACWV5N9M2RV99hQ!enxjr_gVpOmo6geh-OR88IUeabvLgDUAr-7j6ibA3Yb_Y5qVqnkJVwCvnr_L9pni$ <https://urldefense.com/v3/__https://www.apache.org/licenses/LICENSE-2.0__;!!ACWV5N9M2RV99hQ!enxjr_gVpOmo6geh-OR88IUeabvLgDUAr-7j6ibA3Yb_Y5qVqnkJVwCvnr_L9pni$> 
>> 
>> The proposed review is 28 days, ending 3 January 2022.
>> If approved, the proposed publication date is 12 January 2022.
>> 
>> Please let us know if anything else is needed.
>> 
>> Regards,
>> Craig
>> 
>> [1] Proposed changes: 
>> [JDO-759] - In Ch 1.6 added definition of terminology “Hint”
>> [JDO-709] - In Ch 6.3, 14.6, 18 and 19 added support for field and property converters
>> 
>> [JDO-749] - In Ch 6, 14.3, 14.6 and 14.10 added support for java.time types as type of a persistent field or property
>> 
>> [JDO-751] - In Ch 6 and 14.6.2 added support for java.lang.Optional
>> 
>> [JDO-689] - In Ch 11.1 renamed property javax.jdo.spi.PropertiesResourceName to javax.jdo.spi.ResourceName
>> 
>> [JDO-690] - In Ch 11.1 renamed property javax.jdo.Name to javax.jdo.option.Name
>> 
>> [JDO-764] - In Ch 11.1 added a note about the usage of the property ConnectionDriverName
>> 
>> [JDO-743] - In Ch 11.4 change reference “java.sun.com”-URLs to “xmlns.jcp.org”
>> 
>> [JDO-745] - In Ch 11.6 and 14.6.2 added support for bitwise operations to JDOQL
>> 
>> [JDO-687] - In Ch 11.8 and 12.5 removed deprecated methods from DataStoreCache and PersistenceManager
>> 
>> [JDO-735] - In Ch 12.6 and 14.6 added try-with-resources support to interfaces PersistenceManager and Query (extends AutoCloseable)
>> 
>> [JDO-760] - In Ch 14.3 and 14.11 replaced the usage of Collection with List with respect to query results
>> 
>> [JDO-734] - In Ch 14.6 added api to save query as a Named Query
>> 
>> [JDO-737] - In Ch 14.6 added new methods to bind query components returning the query instance to make the query api fluent
>> 
>> [JDO-736] - In Ch 14.6.1 added new execute and setParameter methods making use of generics to avoid casting execute results
>> 
>> [JDO-701] - In Ch 14.6.2 added support for further Math methods
>> 
>> [JDO-746] - In Ch 14.6.2 added support for wildcard matching (String method matches) to JDOQL
>> 
>> [JDO-758] - In Ch 14.6.2 clarified the result of a subquery in JDOQL
>> [JDO-652] - In Ch 14 added a new section 10 specifying support for typesafe queries
>> 
>> [2] Proposed specification: 
>> 
>> 
>> Craig L Russell
>> clr@apache.org <ma...@apache.org>
>> 
>> 
>> Craig L Russell
>> clr@apache.org <ma...@apache.org>
>> 

Craig L Russell
clr@apache.org