Change Details

Wmfdata-Python's repo currently lives at https://github.com/wikimedia/wmfdata-python. However, other Data Platform Engineering repos are moving to Gitlab (T368927) so Wmfdata-Python should move as well. The new location should be https://gitlab.wikimedia.org/repos/data-engineering/wmfdata-python. ## Plan [x] Update [metadata.py](https://github.com/wikimedia/wmfdata-python/blob/main/wmfdata/metadata.py) to point to the GitLab repo. [x] [Release](https://github.com/wikimedia/wmfdata-python/blob/main/docs/developing.md#releasing-a-new-version) v2.4 with the changes to `metadata.py`. Users will see the update notification as normal, with the update command still pointing to the GitHub repo. [x] [Import the repository to GitLab](https://docs.gitlab.com/ee/user/project/import/github.html). * We should do this relatively soon after releasing v2.4. Until we do, users who have updated to v2.4 will see a notification on each import that the "The check for a newer release of Wmfdata failed to complete. Consider checking manually." [x] Update the readme in the GitHub repo with a prominent notice that development has moved to GitLab and then archive the repo. * We cannot blank the GitHub repo at this point, because users will continue to use it to fetch the v2.4. [] Update the [Conda-Analytics conda-environment.yml](https://gitlab.wikimedia.org/repos/data-engineering/conda-analytics/-/blob/main/conda-environment.yml) to point to the GitLab repo. Users will not get an update notification pointing to the GitLab repo until they (1) are running v2.4 and (2) we release a subsequent version (e.g. v2.4.1 or v2.5) on GitLab. For that reason, we don't need to send announcement to users until we do 2.

Wmfdata-Python's repo currently lives at https://github.com/wikimedia/wmfdata-python. However, other Data Platform Engineering repos are moving to Gitlab (T368927) so Wmfdata-Python should move as well. The new location should be https://gitlab.wikimedia.org/repos/data-engineering/wmfdata-python. ## Plan [x] Update [metadata.py](https://github.com/wikimedia/wmfdata-python/blob/main/wmfdata/metadata.py) to point to the GitLab repo. [x] [Release](https://github.com/wikimedia/wmfdata-python/blob/main/docs/developing.md#releasing-a-new-version) v2.4 with the changes to `metadata.py`. Users will see the update notification as normal, with the update command still pointing to the GitHub repo. [x] [Import the repository to GitLab](https://docs.gitlab.com/ee/user/project/import/github.html). * We should do this relatively soon after releasing v2.4. Until we do, users who have updated to v2.4 will see a notification on each import that the "The check for a newer release of Wmfdata failed to complete. Consider checking manually." [x] Update the readme in the GitHub repo with a prominent notice that development has moved to GitLab and then archive the repo. * We cannot blank the GitHub repo at this point, because users will continue to use it to fetch the v2.4. [x] Update links across Wikitech and Phabricator [] Update the [Conda-Analytics conda-environment.yml](https://gitlab.wikimedia.org/repos/data-engineering/conda-analytics/-/blob/main/conda-environment.yml) to point to the GitLab repo. Users will not get an update notification pointing to the GitLab repo until they (1) are running v2.4 and (2) we release a subsequent version (e.g. v2.4.1 or v2.5) on GitLab. For that reason, we don't need to send announcement to users until we do 2.

Wmfdata-Python's repo currently lives at https://github.com/wikimedia/wmfdata-python. However, other Data Platform Engineering repos are moving to Gitlab (T368927) so Wmfdata-Python should move as well. The new location should be https://gitlab.wikimedia.org/repos/data-engineering/wmfdata-python. ## Plan [x] Update [metadata.py](https://github.com/wikimedia/wmfdata-python/blob/main/wmfdata/metadata.py) to point to the GitLab repo. [x] [Release](https://github.com/wikimedia/wmfdata-python/blob/main/docs/developing.md#releasing-a-new-version) v2.4 with the changes to `metadata.py`. Users will see the update notification as normal, with the update command still pointing to the GitHub repo. [x] [Import the repository to GitLab](https://docs.gitlab.com/ee/user/project/import/github.html). * We should do this relatively soon after releasing v2.4. Until we do, users who have updated to v2.4 will see a notification on each import that the "The check for a newer release of Wmfdata failed to complete. Consider checking manually." [x] Update the readme in the GitHub repo with a prominent notice that development has moved to GitLab and then archive the repo. * We cannot blank the GitHub repo at this point, because users will continue to use it to fetch the v2.4. [x] Update links across Wikitech and Phabricator [] Update the [Conda-Analytics conda-environment.yml](https://gitlab.wikimedia.org/repos/data-engineering/conda-analytics/-/blob/main/conda-environment.yml) to point to the GitLab repo. Users will not get an update notification pointing to the GitLab repo until they (1) are running v2.4 and (2) we release a subsequent version (e.g. v2.4.1 or v2.5) on GitLab. For that reason, we don't need to send announcement to users until we do 2.