Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jnosql-dev] [nosql-dev] Time for a review?


On Fri, Jun 26, 2020 at 2:02 PM Werner Keil <werner.keil@xxxxxxx> wrote:

Ivar,

 

Thanks for the additional hints.

 

Would what you said for the spec or NoSQL API under EE4J also go for the compatible Implementation, that an Alpha or Beta release does not require a formal review?


Yes, that is how it is defined in the Eclipse Development Process.
 

 

Based on what I know with Eclipse UOMo (an implementation or Extension to the Units of Measurement JSRs) the Technology Projects need a review by the EMO or Technology PMC especially when there are bigger changes, e.g. using Jakarta EE 9 Milestone dependencies would in my understanding be a bigger Change.


You shouldn't release anything other than a milestone when using with the Jakarta EE 9 milestone dependencies anyway, so a release would be out of the question anyway until Jakarta EE 9 is final. So even if it is a bigger change, you wouldn't need a review until you do the actual release (which will be after Jakarta EE 9 is final).

Ivar
 

 

If the requirements under EE4J are different, then I would see a great Benefit in changing JNoSQL to that TLP as soon as it’s possible.

 

Thanks,

Werner

 

Sent from Mail for Windows 10

 

From: Ivar Grimstad
Sent: Friday, June 26, 2020 13:25
To: Werner Keil
Cc: nosql developer discussions; jnosql developer discussions
Subject: Re: [nosql-dev] Time for a review?

 

Whether JNoSQL stays with Technology or move to EE4J is entirely up to the project. If you decide to move to EE4J, I guess a mail to the EMO should be sufficient.

 

Regarding Jakarta NoSQL, I agree that a progress review is most realistic. Please start that whenever you're ready by sending an email to the EE4J PMC, and we'll take it from there.

 

Ivar

 

On Fri, Jun 26, 2020 at 12:46 PM Werner Keil <werner.keil@xxxxxxx> wrote:

Hi Ivar,

 

Thanks for the update and clarifications.

 

It is true JNoSQL started a bit earlier than most of Jakarta EE was moved to Eclipse, but actually it should be under EE4J Pretty soon, too, like all the other implementations from Krazo to Yasson or Glassfish.

 

What is the process to move it, or what would justify that to stay with Technology forever just because it was a bit faster?

 

Good to hear the beta Releases can be done without a review, so there was Nothing missed, it seems.

 

From my understanding of the NoSQL state, I don’t see a (Final) release very realistic now or in the next few months. The aim of the new betas would be to adopt Jakarta EE 9 and a Major release is likely just on top of that as a standalone Version. If that goes as planned Jakarta EE 10 could contain it in some form, but especially possible synergies with JPA are something we also have only mentioned (e.g at JCrete) but it was not really explored yet.

 

So I think a Progress Review is the only realistic Option in the next few weeks or the upcoming quarter.

 

Kind Regards,

Werner

 

Sent from Mail for Windows 10

 

From: Ivar Grimstad
Sent: Friday, June 26, 2020 08:28
To: Werner Keil
Cc: nosql developer discussions; jnosql developer discussions
Subject: Re: [nosql-dev] Time for a review?

 

Hi,

 

Let's try not to mix things together.

Eclipse JNoSQL is not under EE4J or Jakarta EE, so let's keep that out of this discussion and leave it to the project and the Technology PMC.

 

For Jakarta NoSQL (the specification project):

- Milestones, alphas, betas can be releases as frequently as the project wants without any review

- For a final release, you MUST go through a release review and a ballot in the Specification Committee

- For a final release to pass, you MUST have a spec/api + tck AND a compatible implementation (in this case Eclipse JNoSQL)

- A specification project must either release or go through a progress review every year (similar to a renewal ballot in the JCP).

 

Since it has been a year since your creation review, you have two options:

 

Option 1: Release Review

Choose this option if you are ready for a release within a reasonable time?. Let's say a month or so. Remember that you need a TCK and a compatible implementation that passes the TCK.

Start this process by notifying the PMC and submit a release PR to https://github.com/jakartaee/specifications

 

Option 2: Progress Review

Choose this option if you are NOT ready to release within a month.

Start this process by notifying the PMC on the PMC mailing list with some statement about your progress.

 

Hope this helps!

 

Ivar

 

 

 

On Thu, Jun 25, 2020 at 2:33 PM Werner Keil <werner.keil@xxxxxxx> wrote:

Ivar/all,

 

Thanks a lot for picking up on the items I raised yesterday in the Spec Committee call.

 

It’s lessons learned by NoSQL but ultimately also helps other specs like MVC.

 

As far as I understand there are at least 3 areas where a review seems necessary at least every few months or even before every release drop.

 

  1. The Spec https://jakarta.ee/specifications/nosql/ which may see Milestone stages like Persistence: https://jakarta.ee/specifications/persistence/3.0/, but not sure, if this happens in a “B03” or similar stage here yet or only once NoSQL really published a M1 or RC3?
  2. The “API” project, based on https://projects.eclipse.org/projects/ee4j.nosql/governance I assume the “B1” or “B2” milestones also should have undergone a review like https://projects.eclipse.org/projects/ee4j.nosql/reviews/0.1.0-release-review by the PMC or whoever is responsible.
  3. The JNoSQL implementation should also have a review for every beta listed under https://projects.eclipse.org/projects/technology.jnosql/governance which was not done for  https://search.maven.org/artifact/org.eclipse.jnosql/jnosql-parent/1.0.0-b2/pom or the “b1” release nearly 6 months earlier.

 

Also it looks like the file headers need to be updated with the current year 2020, that may be the smallest issue, but happy to help with either of the artifacts where it wasn’t done already.

 

HTH,

Werner

 

From: Otavio Santana
Sent: Thursday, June 25, 2020 14:17
To: nosql developer discussions
Subject: Re: [nosql-dev] Time for a review?

 

Hey Ivar, how are you?
I've created a draft PR to the big bang: https://github.com/eclipse-ee4j/nosql/pull/55
Please, go ahead and review it.

 

On Thu, Jun 25, 2020 at 3:58 AM Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx> wrote:

Hi,

 

Just checking in to see how things are going... 

Time flies and it has been a year since the creation review and according to the JESP, it is time for a progress review. Unless you are planning to start a release within a reasonable time.

 

Please let me know. I will do my best to help you through the process.

 

Ivar

 

-- 

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation, Inc.

Community. Code. Collaboration. 

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


 

--

Otávio Santana

 

 


 

--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation, Inc.

Community. Code. Collaboration. 

Join us at our virtual event: EclipseCon 2020 - October 20-22

 


 

--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation, Inc.

Community. Code. Collaboration. 

Join us at our virtual event: EclipseCon 2020 - October 20-22

 



--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation, Inc.

Community. Code. Collaboration. 

Join us at our virtual event: EclipseCon 2020 - October 20-22

Back to the top