ee4j.bean-validation Restructuring Review

assigned to @mdelgado624 and @wbeaton

Discussion with Arjan Tijms. Consider these precedents for security.

Ed pushed back on this level of renaming.

Keep the mailing list the same.
Keep the CI the same.

I hope we don't need to do these, but if we must, we must.

added EMO in Eclipse Foundation / Help Desk label

added IT-prioritylow IT-severitylow labels

assigned to @wbeaton

assigned to @mdelgado624

@mdelgado624 I believe that we need to schedule a restructuring review. Can you please make that happen?

Hello @wbeaton and @mdelgado624 FYI:

From: Edward Burns Edward.Burns@microsoft.com Date: Sunday, September 10, 2023 at 19:36 To: EMO EMO emo@eclipse-foundation.org, emo@eclipse.org emo@eclipse.org Cc: Scott Stark sstark@redhat.com, arjan.tijms@gmail.com arjan.tijms@gmail.com, Ivar Grimstad ivar.grimstad@eclipse-foundation.org Subject: Please help me start a restructuring review to Rename Jakarta Bean Validation to Jakarta Validation Dear EMO,

According to Development Resources/HOWTO/Restructuring Reviews - Eclipsepedia, I must cause Review Documentation to be created.

I had filed GitLab issue 3497 about this and Wayne Beaton asked Maria Delgado to make this happen, but I have not heard anything. It's possible I missed it. If so, my apologies. If not, this email is my attempt to follow the steps in the HOWTO.

"Restructuring review documentation should only be as detailed as it needs to be."

The Jakarta EE Platform Project, in collaboration with the Spec Project lead, Scott Stark, have resolved to rename "Jakarta Bean Validation" to "Jakarta Validation" See https://github.com/jakartaee/validation/issues/183 . This issue requests the necessary work be performed to cause:

The URL https://projects.eclipse.org/projects/ee4j.bean-validation 301 redirects to https://projects.eclipse.org/projects/ee4j.validation .
The content that was at https://projects.eclipse.org/projects/ee4j.bean-validation now shows up at https://projects.eclipse.org/projects/ee4j.validation .
On the Overview tab, all occurrences of "Bean Validation" are replaced with "Validation". "Your project plan must be current. Include the URL for your current plan in your review documentation."

https://github.com/jakartaee/specifications/blob/master/bean-validation/3.1/_index.md

Please let me know how to proceed.

Thanks,

Ed Burns Release co-coordinator for Jakarta EE 11

mentioned in issue #392 (closed)

moved from eclipsefdn/helpdesk#3497 (moved)

assigned to @webmaster

assigned to @jmazanek4ep

changed title from {-Rename https://projects.eclipse.org/projects/ee4j.bean-validation to https://projects.eclipse.org/projects/ee4j.validation-} to ee4j.bean-validation Restructuring Review

changed the description

This restructuring review concluded successfully. @webmaster please make the necessary modifications to the Project resources.

This issue requests the necessary work be performed to cause:

The URL https://projects.eclipse.org/projects/ee4j.bean-validation 301 redirects to https://projects.eclipse.org/projects/ee4j.validation .

The content that was at https://projects.eclipse.org/projects/ee4j.bean-validation now shows up at https://projects.eclipse.org/projects/ee4j.validation .

On the Overview tab, all occurrences of "Bean Validation" are replaced with "Validation". "Your project plan must be current. Include the URL for your current plan in your review documentation."

I"ve updated the PMI and our backend so I think that just leaves the CI instance and the mailing list.

The mailing list can't be renamed, so the options are either to leave it as is, or to create a new list and do a lift-and-shift of subscribers.

@pstankie, can your team schedule a rename of the CI instance? We'll also need to update the bot user id when that happens so please cc me on the ticket.

@pstankie please share with me the link to the ticket the schedule the rename of the CI instance. That way we can link it to this one and close both when we're done.

@mdelgado624 The issue releated to renaming is here eclipsefdn/helpdesk#3728 (closed)

@eburnscc4 Are there anything on github repositories descriptions or naming that needs to be edited ? On repositories:

There are still informations like:

About

Bean Validation API

My suggestion would be for /validation to use “Jakarta Validation”

For /validation-spec to use “Jakarta Validation spec document”

And for /validation-tck to use “Jakarta Validation TCK”

(We should probably merge /validation-spec into /validation, with keeping history. I believe git export + filters can do that)

Ps see https://stackoverflow.com/questions/41811986/git-move-directory-to-another-repository-while-keeping-the-history

@atijmse7y Renaming fo Jenkins is complete, but I haven't changed jobs definitions as they require significant modifications of pipelines definitions and since those jobs haven't been run for long time I don't want to modify+run the jobs untested. Can you take a look at the jobs and maybe adjust pipelines definitions and run jobs or suggest what would be the best course of actions ? Tnx.