... | @@ -5,6 +5,7 @@ The Eclipse Foundation supports three development environments, and is proposing |
... | @@ -5,6 +5,7 @@ The Eclipse Foundation supports three development environments, and is proposing |
|
### Background and Motivation
|
|
### Background and Motivation
|
|
|
|
|
|
The Eclipse Foundation (EF) currently supports three development environments:
|
|
The Eclipse Foundation (EF) currently supports three development environments:
|
|
|
|
|
|
* [Gerrit](https://git.eclipse.org/r) + [Bugzilla](https://bugs.eclipse.org) + [cGit](https://git.eclipse.org/c)
|
|
* [Gerrit](https://git.eclipse.org/r) + [Bugzilla](https://bugs.eclipse.org) + [cGit](https://git.eclipse.org/c)
|
|
* [GitHub](https://github.com)
|
|
* [GitHub](https://github.com)
|
|
* [Eclipse GitLab](https://gitlab.eclipse.org)
|
|
* [Eclipse GitLab](https://gitlab.eclipse.org)
|
... | @@ -20,7 +21,7 @@ To that end the Foundation’s IT team will standardize its code hosting, issue |
... | @@ -20,7 +21,7 @@ To that end the Foundation’s IT team will standardize its code hosting, issue |
|
|
|
|
|
### What’s been done so far
|
|
### What’s been done so far
|
|
|
|
|
|
A dozen projects have already moved, or their migrations are in progress. The Bugzilla->Gitlab import process is functional. A Bugzilla -> GitHub Issues migration script is known to exist but has not been needed yet. A Proof of Concept has been built for the project website transition to a new domain, eclipseprojects.io.
|
|
A dozen projects have already moved, or their migrations are in progress. The Bugzilla-\>Gitlab import process is functional. A Bugzilla -\> GitHub Issues migration script is known to exist but has not been needed yet. A Proof of Concept has been built for the project website transition to a new domain, eclipseprojects.io.
|
|
|
|
|
|
### What needs to be done
|
|
### What needs to be done
|
|
|
|
|
... | @@ -48,8 +49,6 @@ Help Projects migrate from Gerrit/Bugzilla to GitLab or Github: |
... | @@ -48,8 +49,6 @@ Help Projects migrate from Gerrit/Bugzilla to GitLab or Github: |
|
* Create server redirects to ensure existing links to bugs function
|
|
* Create server redirects to ensure existing links to bugs function
|
|
* https://bugs.eclipse.org/bugs would go to the paginated index
|
|
* https://bugs.eclipse.org/bugs would go to the paginated index
|
|
* https://bugs.eclipse.org/bugs/show_bug.cgi?bug_id=XYZ would redirect to the static html page of that bug
|
|
* https://bugs.eclipse.org/bugs/show_bug.cgi?bug_id=XYZ would redirect to the static html page of that bug
|
|
|
|
|
|
|
|
|
|
* Long Term Git Data retention
|
|
* Long Term Git Data retention
|
|
* At this time, all Gerrit repositories should be marked as “Read Only” with links to the new location
|
|
* At this time, all Gerrit repositories should be marked as “Read Only” with links to the new location
|
|
* Disable Gerrit Code Review system 6 months after the last project has migrated
|
|
* Disable Gerrit Code Review system 6 months after the last project has migrated
|
... | @@ -57,7 +56,7 @@ Help Projects migrate from Gerrit/Bugzilla to GitLab or Github: |
... | @@ -57,7 +56,7 @@ Help Projects migrate from Gerrit/Bugzilla to GitLab or Github: |
|
|
|
|
|
### Proposed timeline
|
|
### Proposed timeline
|
|
|
|
|
|
Throughout the entirety of this timeline, the IT team will use mailng lists, [eclipsestatus.io](https://eclipsestatus.io), Twitter and other means of communicating with projects the upcoming activities ahead of time.
|
|
Throughout the entirety of this timeline, the IT team will use mailng lists, eclipsestatus.io, Twitter and other means of communicating with projects the upcoming activities ahead of time.
|
|
|
|
|
|
#### Jan-Mar 2022 COMPLETED
|
|
#### Jan-Mar 2022 COMPLETED
|
|
|
|
|
... | @@ -77,7 +76,7 @@ Move project website repos. This will require: |
... | @@ -77,7 +76,7 @@ Move project website repos. This will require: |
|
|
|
|
|
* ~~Changes to the checkout script~~
|
|
* ~~Changes to the checkout script~~
|
|
* ~~A modification to projects.eclipse.org to allow the specification of a ‘website repo’~~
|
|
* ~~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.
|
|
* 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 <span dir="">\~</span>50% of projects use projects.eclipse.org as their default website.
|
|
|
|
|
|
#### Oct-Dec 2022 COMPLETED
|
|
#### Oct-Dec 2022 COMPLETED
|
|
|
|
|
... | @@ -85,35 +84,34 @@ Move project website repos. This will require: |
... | @@ -85,35 +84,34 @@ Move project website repos. This will require: |
|
|
|
|
|
* One announcement made November 14, 2022
|
|
* 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.
|
|
* 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 -\> GL import working~~
|
|
* BZ -> GH Issues import unknown; tool selected https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/679
|
|
* BZ -\> GH Issues import unknown; tool selected https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/679
|
|
* 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
|
|
* 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
|
|
|
|
|
|
|
|
|
|
#### Jan-Mar 2023
|
|
#### Jan-Mar 2023
|
|
|
|
|
|
**Test** Bugzilla to GH Issues tool, and re-test Bugzilla to GL Issues too.
|
|
**Test** Bugzilla to GH Issues tool, and re-test Bugzilla to GL Issues too.
|
|
|
|
|
|
* https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/679
|
|
* https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/679
|
|
* 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
|
|
* 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.
|
|
**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
|
|
#### April 2023 - June 2024
|
|
|
|
|
|
* ~~[Q2 moves due May 15, Q3 July] Perform migrations and select more projects to notify/move for the following quarter.~~
|
|
* ~~\[Q2 moves due May 15, Q3 July\] Perform migrations and select more projects to notify/move for the following quarter.~~
|
|
* [Denis is on it, needed for IPZilla too] Build a static Proof-Of-Concept Bugzilla instance. (pagination based on project, not bug numbers)
|
|
* \[Denis is on it, needed for IPZilla too\] Build a static Proof-Of-Concept Bugzilla instance. (pagination based on project, not bug numbers)
|
|
* ~~[Matt ML mid-May] Communicate overall progress as we go along.~~
|
|
* ~~\[Matt ML mid-May\] Communicate overall progress as we go along.~~
|
|
* [2023-08-22] Jakub to pick 2023-Q4 projects, and communicate with them by Sept 8.
|
|
* \[2023-08-22\] Jakub to pick 2023-Q4 projects, and communicate with them by Sept 8.
|
|
* [Matt ML mid-Oct] Communicate overall progress as we go along.
|
|
* \[Matt ML mid-Nov\] Communicate overall progress as we go along.
|
|
|
|
|
|
#### Oct 2024
|
|
#### Oct 2024
|
|
|
|
|
|
* Send service shutdown reminder notices for Gerrit/Bugzilla/Cgit targeting May 2025
|
|
* Send service shutdown reminder notices for Gerrit/Bugzilla/Cgit targeting May 2025
|
|
* Test service URL redirections
|
|
* Test service URL redirections
|
|
|
|
* Schedule Gerrit brownouts
|
|
|
|
|
|
#### May 2025
|
|
#### May 2025
|
|
|
|
|
... | @@ -122,6 +120,8 @@ Move project website repos. This will require: |
... | @@ -122,6 +120,8 @@ Move project website repos. This will require: |
|
* Take the final snapshot of Bugzilla and deploy a static copy
|
|
* Take the final snapshot of Bugzilla and deploy a static copy
|
|
* Shutdown Bugzilla
|
|
* Shutdown Bugzilla
|
|
* Archive Bugzilla data and configs, with a 6 month recovery window.
|
|
* Archive Bugzilla data and configs, with a 6 month recovery window.
|
|
|
|
* Investigate possible redirects for cGit to current project repos
|
|
|
|
* Check logs for cGit activity to see if it's even worth it
|
|
|
|
|
|
#### May 2025 - Dec 2026
|
|
#### May 2025 - Dec 2026
|
|
|
|
|
... | | ... | |