... | ... | @@ -4,7 +4,10 @@ The Eclipse Foundation supports three development environments, and is proposing |
|
|
|
|
|
### Background and Motivation
|
|
|
|
|
|
The Eclipse Foundation (EF) currently supports three development environments: Gerrit + Bugzilla + cGit GitHub Eclipse GitLab (<https://gitlab.eclipse.org>)
|
|
|
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)
|
|
|
* [GitHub](https://github.com)
|
|
|
* [Eclipse GitLab](https://gitlab.eclipse.org)
|
|
|
|
|
|
The current proposal is based on the following motivations:
|
|
|
|
... | ... | @@ -40,17 +43,19 @@ Help Projects migrate from Gerrit/Bugzilla to GitLab or Github: |
|
|
* Actual implementation may vary
|
|
|
* Archive all 550,000 bugs individually as one static html page per bug
|
|
|
* Disable the Bugzilla Perl application
|
|
|
* 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/show_bug.cgi?bug_id=XYZ> would redirect to the static html page of that bug
|
|
|
* 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/show_bug.cgi?bug_id=XYZ would redirect to the static html page of that bug
|
|
|
|
|
|
|
|
|
* Long Term Git Data retention
|
|
|
* 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
|
|
|
* Add links from <https://git.eclipse.org/r> to the cGit browser, <https://git.eclipse.org/c> and maintain cGit functionality, with clear indications that the repos shown are archived, for two years. This will allow developers to browse the code as it was snapshotted at the time of migration.
|
|
|
* Add links from https://git.eclipse.org/r to the cGit browser, https://git.eclipse.org/c and maintain cGit functionality, with clear indications that the repos shown are archived, for two years. This will allow developers to browse the code as it was snapshotted at the time of migration.
|
|
|
|
|
|
### Proposed timeline
|
|
|
|
|
|
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.
|
|
|
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.
|
|
|
|
|
|
#### Jan-Mar 2022
|
|
|
|
... | ... | @@ -73,7 +78,7 @@ Move project website repos. This will require: |
|
|
|
|
|
#### Oct-Dec 2022
|
|
|
|
|
|
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.
|
|
|
**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.
|
|
|
|
|
|
#### Jan-Mar 2023
|
|
|
|
... | ... | |