Bugzilla – Full Text Bug Listing
| Summary: | Merge the PolarSys forge into Eclipse.org | ||
|---|---|---|---|
| Product: | Community | Reporter: | Wayne Beaton <wayne.beaton> |
| Component: | Project Management & Portal | Assignee: | Wayne Beaton <wayne.beaton> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | benoit.langlois, benoit.viaud, boubekeur.zendagui, charles, chris.guindon, daniel.exertier, denis.roy, etienne.juliot, florent.garin, frederic.madiot, gael.blondelle, huascar.espinoza, Jean.Casteres, jonathan.dumont, laurent.spaggiari, m.bouet, philippe.dul, pierre-charles.david, raphael.faudou, silvia.mazzini, sofyan.su, stephane.bonnet, thomas.guiu, wayne.beaton, webmaster, yupanqui.munozjulho |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | 541053, 543319, 543320, 543321, 543322, 543325, 543326, 543543, 543664, 543694, 543695, 543697, 544194, 547521, 552859 | ||
| Bug Blocks: | |||
|
Description
Wayne Beaton
As part of this exercise, we're also going to merge the polarsys.org listserv into eclipse.org. e.g. chess-dev@polarsys.org will become chess-dev@eclipse.org We have planned a Capella release train until mid/end- January 2019. Is it possible to wait for this date? What would be the time of unavailability, especially for Jenkins? (In reply to Benoit Langlois from comment #2) > We have planned a Capella release train until mid/end- January 2019. > Is it possible to wait for this date? Yes. > What would be the time of unavailability, especially for Jenkins? We'll need the webmaster and CBI team to coordinate this move with the project teams. So you get a say in this decision. I've created Bug 543319 as a blocker to address this; please use that bug to track this process. The final steps of this process will be: * Change the identifiers for PolarSys Projects in the foundation db and IPZilla (e.g. polarsys.polarsys.capella becomes polarsys.capella) * Shut down www.polarsys.org with redirect to projects.eclipse.org/projects/polarsys This change will have the following impacts on the committers and community: * www.polarsys.org will redirect to projects.eclipse.org/projects/polarsys * Git repository remotes will be changed from git.polarsys.org to git.eclipse.org * Builds will move to Eclipse CBI infrastructure * Mailing lists will change from *@polarsys.org to *@eclipse.org * bugs.polarsys.org will redirect to bugs.eclipse.org * wiki.polarsys.org will redirect to wiki.eclipse.org * polarsys.org/forums will redirect to eclipse.org/forums Note that technical namespaces (e.g. package/bundle names) do not need to change. As part of this migration, we will ensure that the Eclipse Trademark Guidelines are applied. e.g. "*Eclipse* Kitalpha". Note that no formal review is required for this primarily organizational change. Without any request from a project, the migration can start from Monday, Jan. 28th. In the list of impacts, the on-line Help [1] was forgotten. [1] https://help.polarsys.org/help/index.jsp I've moved the basic content for all of the projects that we're going to move. * Eclipse B612 * Eclipse Capella * Eclipse CHESS * Eclipse Kitalpha * Eclipse LibIMS * Eclipse NG661 Designer * Eclipse OpenCert * Eclipse PolarSys 3P * Eclipse Product Lifecycle Management Platform * Eclipse Safety Framework * Eclipse Time4Sys Note that I've realigned all project names to use the "Eclipse" brand. I've created bugs to track termination reviews for the others. Specifically: * PolarSys COTSAQ * PolarSys Rover * PolarSys POP * PolarSys ReqCycle You can access of these directly from the PolarSys Top Level project's page. https://www.polarsys.org/projects/polarsys The committer and project lead election functionality will work from these pages. I'll need to coordinate the rest of the move with webmaster. We'll update the rest of the metadata as part of that work. Hello. We enter in a red zone of release for Kitalpha and Capella. The green zone will start from June 15th. Bugzilla, Git/Gerrit, Jenkins, Download must NOT be migrated during this period. Other tools are not concerned (Help, Forum, Wiki...). Thank you. (In reply to Benoit Langlois from comment #9) > Hello. We enter in a red zone of release for Kitalpha and Capella. The green > zone will start from June 15th. Bugzilla, Git/Gerrit, Jenkins, Download must > NOT be migrated during this period. Other tools are not concerned (Help, > Forum, Wiki...). Thank you. Thanks for letting us know. The webmaster will coordinate with the project team before making any changes. Note that the Capella project's URL that we use to communicate is https://www.polarsys.org/capella/ (not https://www.polarsys.org/projects/polarsys.capella). So we will also need a redirect from this actual URL to the new one (https://www.eclipse.org/capella). I have scheduled termination reviews that will conclude on June 19/2019 for COTSAQ, POP, ReqCycle, and Rover. Bug 543664, Bug 543697, Bug 543694, Bug 543695 Any news on this migration? What are the next planned steps? We're going to complete this move during the week of December 2/2019. Note that some of the tasks will result in some disruption for committers and the community. e.g., * Mailing lists will move from @polarsys.org to @eclipse.org (bug 543322); and * Git repositories will move from git.polarsys.org to git.eclipse.org (bug 544194). I will send a note to the PMC and WG mailing lists later today. Can/should we send out reminders that this work is starting today? OK from the Thales side. Are we good to close this now? -M. I believe that we're done. |