There was a discussion and decision to move the Specification Projects into the
https://github.com/jakartaee/ github. We didn't do it prior to Jakarta EE 8 because it would involve some work by Eclipse infra and we didn't want to risk pushing out the release date.
Now that we're on the other side of the release, and if people have appetite to move/rename repos (breaking their CI), we should do both things at the same time to minimize the changes.
For just the rename within the existing eclipse-ee4j repo, the CI wouldn't necessarily break, as Github would automatically redirect.
I like that one too tbh. Must have missed it before, or my overloaded brain didn't register it at the time :P
I created a prototype of the org -- this doesn't reflect the proposed name changes, but it could.
Arjan, I've added you as an Owner of the mock org so you can play around with the spec renames and we can have a complete looking proposal.
Oh wow, you've been busy!
I'll play around a little with that this weekend.
Btw, is this project renaming something for the Jakarta EE Specification Committee to discuss next week?
Kind regards,
Arjan
Hi,
Now that Jakarta EE 8 is released, shall we start with renaming some of the projects to their Jakarta names?
In a GitHub rename, GitHub automatically creates a redirect from the old name (jaspic) here, so the impact should be minimal. I'll nevertheless will be updating the Jenkins scripts etc to use the new name then.
Thoughts?
Kind regards,
Arjan
_______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec
