I hope the slight deviation from Bill Shannon’s https://wiki.eclipse.org/JakartaEE_Maven_Versioning_Rules by dropping the extra digits are not a problem? It seems Maven does the digit padding here, so from a Maven dependency perspective it looks like it should work. Werner Sent from Mail for Windows 10 We'll run the Jenkins deploy this weekend.
But we'll use the B prefix on it. I thought something like the Spec Committee also reviewing those Milestones was discussed in the call of last weeek, but the discussion did not seem finished there yet and we ran out of time or had to move onto other Topics. I meant this draft review by whoever does it, not the Final spec Ballot. Werner I'm not subscribed to the lists, please feel free to forward my responses to the list. I believe Otavio spoke about „compatibility with Java 11 and Java 8“ otherwise no such Claim was mentioned here was it?
I was explaining the rule, out of concern that your statement about regarding the need for a specification committee vote might be misunderstood as being a requirement for a milestone build. Once the Spec/API progressed of course there can be a Milestone of JNoSQL, the same goes for Glassfish even though it isn’t Jakarta EE 9 compatible at this point either. Good idea that Otavio also directly may reach out to the Spec Committee, can he write on the list after subscribing? I assume he can, as we have some other “guests” who even participate informally in some of the votes.
Otavio should just use the public list. Or you, as a member of the specification committee, can advocate on behalf of the project if you feel that a more direct connection is required. But using the public list is preferred. Werner No claims of compatibility may be made based on the implementation of specification that has not been ratified as a "final specification" as defined by the specification process. I don't believe that anybody is making any such claims. However, clearly labeled milestone builds (we tend to avoid using the term "release" when referring to milestones) are fine. In fact, they're encouraged. I do recommend that you start the process of socializing the pending release of the Jakarta NoSQL specification with the specification committee. We're going to need them to engage in a ballot to ratify the release; this will go more smoothly if they know that it's coming. Otavio, While it seems to apply to the implementation (JNoSql) please note, for the Jakarta EE spec we have to undergo a review and vote by the Spec Committee and not everything seems to be written in a handbook here, so ask the mentors or EMO (Wayne) for advice. We started with a slightly malformatted 1.0.0-b1, but it should rather be like “b02“ or “B02“ now, also please let’s coordinate and try to stick to a common naming and numbering pattern that MVC is also likely to use in the near future, so ask Ivar before pushing or staging anything that might be acceptable to Maven but could deviate from how the other specs do it. Werner · Update the MongoDB, Cassandra drivers · Update Javadoc documentation · Update Ref documentation · Creates TCK Mapping · Creates TCK Communication · Creates TCK Driver · Remove Async APIs · Keep the compatibility with Java 11 and Java 8 · Defines Reactive API as an extension --
-- Wayne Beaton Director of Open Source Projects | Eclipse Foundation, Inc. Join us at our virtual event: EclipseCon 2020 - October 20-22
-- Wayne Beaton Director of Open Source Projects | Eclipse Foundation, Inc. Join us at our virtual event: EclipseCon 2020 - October 20-22 _______________________________________________
nosql-dev mailing list
nosql-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/nosql-dev
-- |
