Minutes: JDO TCK Conference Call Thursday Jan 20 11 AM PST 20 CET
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell Next meeting: Thursday January 27 11:00 Pacific 20:00 CET Agenda: 1. DB website migration AI Craig ask infra for a mail list gene...@db.apache.org and notificati...@db.apache.org to discuss the web site. Also ask if all committers to derby, torque, and jdo can commit. 2. JCP JSR-243 - Maintenance Review 5 https://www.jcp.org/en/jsr/detail?id=243 - Maintenance Review Ballot https://www.jcp.org/en/jsr/results?id=6302 results: 17 yes 1 not voted One comment was asking whether J2EE was still relevant. AI Craig look at the specification and see if we should update the J2EE reference to Jakarta or keep it and assume that people know what the J2EE story is. AI Craig ask JCP to publish the 3.2 dtd and xsd files. AI Craig ask Oracle to redirect their JDO web page. 3. JDO 3.2 Release AI Tilmann: finish the 3.2 release in git; call a vote for the 3.2 on the jdo-dev list. The PMC will need to approve it. 4. INFRA Ticket "Change "Apache Rules" in Nexus to check for sha256/512 instead of sha1/md5" https://issues.apache.org/jira/browse/INFRA-22540 Tilmann will use the new guidance and update the release instructions as appropriate. The end result should be that there are no problems publishing the release artifacts to maven (needs .md5 and .sha1) and no md5 or sha1 artifacts published to dist.apache.org site. 5. Issues with Fix Version JDO-3.2 https://issues.apache.org/jira/issues/?jql=project%20%3D%20JDO%20AND%20fixVersion%20%3D%20%22JDO%203.2%22 6. Other issues Action Items from weeks [Dec 09 2021] AI Craig: Try to contact all current/former participants in JDO development and see if and how they want to be recognized on the JDO and DB web sites. https://db.apache.org/whoweare.html [Dec 02 2021] AI Tobias: find how to update and generate the db.apache.org web site. Message priv...@db.apache.org and ask if anyone has the latest information. If no response, ask us...@infra.apache.org for the truth. [Oct 07 2021] AI Craig send a private message to all JSR-243 Expert Group members asking if they wish to continue. [Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts [Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL datastores":https://issues.apache.org/jira/browse/JDO-651? Craig L Russell c...@apache.org
[jira] [Updated] (JDO-671) Oracle spec page on JDO does not list mrel 3/JDO 3.0
[ https://issues.apache.org/jira/browse/JDO-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-671: - Fix Version/s: JDO 3.3 (was: JDO 3.2) > Oracle spec page on JDO does not list mrel 3/JDO 3.0 > > > Key: JDO-671 > URL: https://issues.apache.org/jira/browse/JDO-671 > Project: JDO > Issue Type: Improvement > Components: specification >Affects Versions: JDO 3 (3.0) >Reporter: Matthew T. Adams >Assignee: Craig L Russell >Priority: Trivial > Fix For: JDO 3.3 > > > The page at > http://www.oracle.com/technetwork/java/index-jsp-135919.html > does not list JDO maintenance release 3 or JDO 3.0 but should. -- This message was sent by Atlassian Jira (v8.20.1#820001)
Re: Successful Maintenance Ballot
Congratulations! bryan On Wed, Jan 19, 2022 at 1:36 PM Craig Russell wrote: > > Hi, > > The Maintenance Review 5 for JDO closed with a successful vote. > https://jcp.org/en/jsr/results?id=6302 > > 17 voted Yes and there was one comment: > On 2022-01-14 Fogel, Ken voted Yes with the following comment: > I am puzzled that the term J2EE appears. I was under the impression it had > been retired. Is this also part of Jakarta? > > We should discuss detailed next steps at Thursday's meeting. > > Craig > > Craig L Russell > c...@apache.org >
[jira] [Commented] (JDO-744) XSD/DTD not published for JDO 3.1
[
https://issues.apache.org/jira/browse/JDO-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17479185#comment-17479185
]
Andy Jefferson commented on JDO-744:
Can we make sure that this is done for the v3.2 variants also, at release?
People can't be advised to include
"{{{}http://xmlns.jcp.org/xml/ns/jdo/jdo_3_2.xsd;
{}}}
in their XML file when it doesnt exist.{{{}{}}}
> XSD/DTD not published for JDO 3.1
> -
>
> Key: JDO-744
> URL: https://issues.apache.org/jira/browse/JDO-744
> Project: JDO
> Issue Type: Bug
> Components: api
>Affects Versions: JDO 3.1
>Reporter: Andy Jefferson
>Assignee: Craig L Russell
>Priority: Major
> Fix For: JDO 3.2
>
>
> Should be on
> http://xmlns.jcp.org/xml/ns/jdo/jdo_3_1.xsd
> http://xmlns.jcp.org/dtd/jdo_3_1.dtd
> No idea how they are to get on that private server. Perhaps someone knows?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
