I just tried following the steps to create a 1.0 release and it does indeed allow a release plan to be created, meaning the link below now works, and is populated with what I filled out. I had to arbitrarily
fill in a target release date, which I set to some day in December. We can change it later, as well as the other items in the list. I tried to capture things we have been working on thus far. Notably, there is nothing there about REST, which is listed in
the original Jakarta Data document but which we have not been working on at all yet, and I was never clear enough on what was intended in that space. Hopefully, someone else can fill that part in.
From:
data-dev <data-dev-bounces@xxxxxxxxxxx> on behalf of Nathan Rauh <nathan.rauh@xxxxxxxxxx>
Date: Monday, February 20, 2023 at 11:41 AM
To: data developer discussions <data-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] Re: [data-dev] Release a new beta version [b2]
In that issue discussion, Werner provides links to example release plans, https: //projects. eclipse. org/projects/technology. uomo/releases/0. 8. 0/plan https: //projects. eclipse. org/projects/ee4j. jakartaconfig/releases/0. 1/plan
If you try the same
This Message Is From an External Sender
|
This message came from outside your organization.
|
|
|
In that issue discussion, Werner provides links to example release plans,
https://projects.eclipse.org/projects/technology.uomo/releases/0.8.0/plan
https://projects.eclipse.org/projects/ee4j.jakartaconfig/releases/0.1/plan
If you try the same for Jakarta Data, it just sends you back to the main page for Jakarta Data
https://projects.eclipse.org/projects/ee4j.data/releases/1.0/plan
Maybe we need to create the 1.0 release first? That seems backwards to me. Intuitively I would expect to create a plan for a release before creating a release.
From:
data-dev <data-dev-bounces@xxxxxxxxxxx> on behalf of Otavio Santana <otaviopolianasantana@xxxxxxxxx>
Date: Monday, February 20, 2023 at 11:11 AM
To: data developer discussions <data-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] Re: [data-dev] Release a new beta version [b2]
Hey Nathan. Please, check this Ivar's thread: https: //github. com/jakartaee/specifications/pull/587#issuecomment-1384220681 The plan's reviews look like the Changelog.
On Mon, Feb 20, 2023 at 4: 21 PM Nathan Rauh <nathan. rauh@ us. ibm. com>
This Message Is From an External Sender
|
This message came from outside your organization.
|
|
|
Hey Nathan.
The plan's reviews look like the Changelog.
On the topic of the Plan Review, does anyone know how to create one?
If I browse to the project for Jakarta Data,
https://projects.eclipse.org/projects/ee4j.data, I only see options for Progress Review and New Release:

The Eclipse documentation for creating a Project Plan
https://www.eclipse.org/projects/dev_process/#4_10_Plans
says “Project Plans must be delivered to the community through communication channels approved by the EMO” but doesn’t give specific detail or links.
That would be the nice move. Release a version with Repository and pagination is great for the first version. On Mon, Feb 20, 2023,
10: 44 Werner Keil <werner. keil@ gmx. net> wrote: What about the Plan Review? Gesendet von Mail für Windows Von:
This Message Is From an External Sender
|
This message came from outside your organization.
|
|
|
That would be the nice move.
Release a version with Repository and pagination is great for the first version.
What about the Plan Review?
Gesendet von
Mail
für Windows
Hello everyone, after a couple of discussions on the API, we get progress on it; plus, we need enough maturity to publish a new beta version and
a plan to the Jakarta EE committee.
Please, let me know your thoughts.
Well, not entirely true. As I explained
here,
you still need to produce a plan for Jakarta Data and engage in a plan review according to the JESP.
Since there is no plan on record approved by the specification committee, so the answer to the first question would be "No", and then follow from
there.
--
Ivar Grimstad
Jakarta EE Developer Advocate |
Eclipse Foundation
Eclipse Foundation
- Community. Code. Collaboration.
_______________________________________________
data-dev mailing list
data-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org
--
_______________________________________________
data-dev mailing list
data-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org
_______________________________________________
data-dev mailing list
data-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org
--
|