... | ... | @@ -79,7 +79,7 @@ Move project website repos. This will require: |
|
|
* ~~A modification to projects.eclipse.org to allow the specification of a ‘website repo’~~
|
|
|
* NOTE: Only projects that are actually using their website repositories will be moved. If a project website repo contains only the default redirection to projects.eclipse.org that repo will be replaced with a server-side redirection to projects.eclipse.org. Currently it appears that \~50% of projects use projects.eclipse.org as their default website.
|
|
|
|
|
|
#### Oct-Dec 2022
|
|
|
#### Oct-Dec 2022 COMPLETED
|
|
|
|
|
|
**Announce** compulsory migrations (GitLab as default) starting with the least active projects, and adding some redirects on Gerrit to point at the new locations. Work to commence in April 2023, and target June 2024 as the move end date.
|
|
|
|
... | ... | @@ -95,7 +95,7 @@ Move project website repos. This will require: |
|
|
**Test** Bugzilla to GH Issues tool, and re-test Bugzilla to GL Issues too.
|
|
|
* Bugzilla product marked as read-only (Not open to new bugs), comment added that mentions the new location of this project's issues, then leave as-is
|
|
|
|
|
|
**Identify** 15-20 projects to move in Q2 (April-June).
|
|
|
~~**Identify** 15-20 projects to move in Q2 (April-June). ~~
|
|
|
|
|
|
**Notify** their -dev mailing lists and create a tracking issue on GitLab HelpDesk. We will be flexible and accommodating with projects and the plans for migrations. If a project is non-responsive after 30 days of contacting them to establish a migration plan, we will work with the Foundation's project team to determine if the project is still active and terminate inactive projects, or migrate to GitLab by default.
|
|
|
|
... | ... | |