[jpa-dev] Action needed: Certification Requests for Hibernate ORM

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[jpa-dev] Action needed: Certification Requests for Hibernate ORM

From: Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 3 Jun 2021 07:57:00 +0200
Delivered-to: jpa-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/jpa-dev/>
List-help: <mailto:jpa-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/jpa-dev>, <mailto:jpa-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/jpa-dev>, <mailto:jpa-dev-request@eclipse.org?subject=unsubscribe>

Hi,

I don't know if you've noticed, but HIbernate ORM has filed certification requests for Jakarta Persistence 2.2 and 3.0:

https://github.com/eclipse-ee4j/jpa-api/issues/323

https://github.com/eclipse-ee4j/jpa-api/issues/324

Actions needed:

1. Please add the 'certification' label to these issues

2. When/if approved, add the 'accepted' label and close the issue

Per the TCK Process, a certification request is approved by either of these scenarios:

- Approval by lazy consensus after a period of two weeks (14 days), or

- Approval by a majority vote of the specification project as soon as it happens, or
- Approval by any of the specification project leads at any time

Ivar

--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration.

Prev by Date: Re: [jpa-dev] An Attempt at Triaging Issues
Next by Date: [jpa-dev] Is AutoCloseable support the only expected feature change for Jakarta Persistence 3.1?
Previous by thread: [jpa-dev] Plan review for Jakarta Persistence 3.1 completed!
Next by thread: [jpa-dev] Is AutoCloseable support the only expected feature change for Jakarta Persistence 3.1?
Index(es):
- Date
- Thread

Back to the top