Bugzilla – Full Text Bug Listing
| Summary: | Fully change project name for Jakarta Messaging | ||
|---|---|---|---|
| Product: | Community | Reporter: | arjan tijms <arjan.tijms> |
| Component: | Process | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | frederic.gurr, mihalyi, wayne.beaton |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
arjan tijms
+1 Webmaster, the id of the project will change from ee4j.jms to ee4j.messaging. Arjan, do you want Github repository names changed as well? We can't rename the mailing list, would you prefer to keep the current one, or have us create a new one? Also since you're using github issues can I remove the JMS bugzilla product(there are no bugs currently)? -M. > Arjan, do you want Github repository names changed as well? Yes, please. > We can't rename the mailing list, would you prefer to keep the current one, or have us create a new one? Let's create a new one then. Does that archive the existing one? Can mails be moved to the new one? Would be great if possible, but not strictly necessary. The list doesn't have a super high volume of mails. > Also since you're using github issues can I remove the JMS bugzilla product(there are no bugs currently)? Yes, we don't use it. Thanks! (In reply to arjan tijms from comment #3) > > Arjan, do you want Github repository names changed as well? > > Yes, please. The new names for the GitHub repositories should be: * jms-api => messaging-api * jms-proposals => messaging-proposals Correct? > The new names for the GitHub repositories should be: > * jms-api => messaging-api > * jms-proposals => messaging-proposals > Correct? Just jms-api -> messaging would be fine. I see we're not entirely consistent, unfortunately, but we have: https://github.com/eclipse-ee4j/authentication https://github.com/eclipse-ee4j/authorization And also http://github.com/eclipse-ee4j/security-api http://github.com/eclipse-ee4j/interceptor-api As we'd like to emphasise the simplest term, I think just https://github.com/eclipse-ee4j/messaging would be best. Ok. Just to double-check: * jms-proposals => messaging-proposals is correct? > * jms-proposals => messaging-proposals
> is correct?
Yes, it is. Thanks!
While renaming the GitHub repositories, I noticed that there is a third JMS/Messaging related repo: https://github.com/eclipse-ee4j/genericjmsra Should it be renamed as well? Good find. Yes, that should become genericmessagingra then. GitHub repos have been renamed * https://github.com/eclipse-ee4j/messaging * https://github.com/eclipse-ee4j/messaging-propsals * https://github.com/eclipse-ee4j/genericmessagingra Committers will need to adjust their remotes, etc. > GitHub repos have been renamed Thanks! > Committers will need to adjust their remotes, etc. They should, but at the same time, Github handles renames transparently by putting a working redirect into place (works for web visits, pulls, pushes, etc). (In reply to arjan tijms from comment #3) > Let's create a new one then. Does that archive the existing one? Can mails > be moved to the new one? Would be great if possible, but not strictly > necessary. The list doesn't have a super high volume of mails. Ok, I've created messaging-dev as the new ML and subscribed all current members of jms-dev. While we can't move the messages, the jms-dev archive will remain online. I've closed jms-dev to new posts, and posted a 'list has moved' note. -M. > Ok, I've created messaging-dev as the new ML and subscribed all current members of jms-dev. While we can't move the messages, the jms-dev archive will remain online. I've closed jms-dev to new posts, and posted a 'list has moved' note.
That's sounds absolutely perfect. Thank you again!
The CI related renaming is done. Please test all build jobs and let us know if anything is still missing. Thank you for creating a new mailing list messaging-dev. Can you also update the description of the old ML at https://accounts.eclipse.org/mailing-list/jms-dev to explain that the list is archived and messaging-dev should be used instead? There are still a lot of resources on the internt that point to the old mailing list and the page doesn't redirect to the new ML. I suggest the following description on jms-dev ML: ----------- This list is archived. This list was used for technical discussions related to Jakarta Messaging. It's now superseded by the messaging-dev list (https://accounts.eclipse.org/mailing-list/messaging-dev). (In reply to Ondrej Mihalyi from comment #15) Done. -M. |