... | ... | @@ -83,9 +83,21 @@ Move project website repos. This will require: |
|
|
|
|
|
**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.
|
|
|
|
|
|
* One announcement made November 14, 2022
|
|
|
* One announcement planned December 14, 2022. Projects are welcome to immediately plan a date in the future that is convenient for them, by filing a HelpDesk issue, but those projects that do NOT make their timing preference known will be required to move as webmasters will randomly select 15-20 migrations per quarter until June 2024.
|
|
|
* BZ -> GL import working
|
|
|
* BZ -> GH Issues import unknown; tool selected (dig up the issue)
|
|
|
|
|
|
|
|
|
#### Jan-Mar 2023
|
|
|
|
|
|
Identify 15-20 projects to move in Q2 (April-June). We will send notices to 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.
|
|
|
**Test** Bugzilla to GH Issues tool, and re-test Bugzilla to GL Issues too.
|
|
|
|
|
|
**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.
|
|
|
|
|
|
|
|
|
|
|
|
#### April 2023 - June 2024
|
|
|
|
... | ... | |