| ... | @@ -280,22 +280,31 @@ TPA with the before/after names, and how they should be handled. |
... | @@ -280,22 +280,31 @@ TPA with the before/after names, and how they should be handled. |
|
|
For example, here's the table of repositories migrated by the
|
|
For example, here's the table of repositories migrated by the
|
|
|
applications team:
|
|
applications team:
|
|
|
|
|
|
|
|
| Gitolite | GitLab | fate |
|
|
| Gitolite | GitLab | fate |
|
|
|
|----------------------------|--------------------------------------|---------|
|
|
|----------------------------|--------------------------------------|----------|
|
|
|
| builders/tor-browser-build | tpo/applications/tor-browser-build | migrate |
|
|
| builders/tor-browser-build | tpo/applications/tor-browser-build | migrated |
|
|
|
| builders/rbm | tpo/applications/rbm | migrate |
|
|
| builders/rbm | tpo/applications/rbm | migrated |
|
|
|
| tor-android-service | tpo/applications/tor-android-service | migrate |
|
|
| tor-android-service | tpo/applications/tor-android-service | migrated |
|
|
|
| tor-browser | tpo/applications/tor-browser | migrate |
|
|
| tor-browser | tpo/applications/tor-browser | migrated |
|
|
|
| tor-browser-spec | tpo/applications/tor-browser-spec | migrate |
|
|
| tor-browser-spec | tpo/applications/tor-browser-spec | migrated |
|
|
|
| tor-launcher | tpo/applications/tor-launcher | archive |
|
|
| tor-launcher | tpo/applications/tor-launcher | archived |
|
|
|
| torbutton | tpo/applications/torbutton | archive |
|
|
| torbutton | tpo/applications/torbutton | archived |
|
|
|
|
|
|
|
|
The above shows 5 repositories that should be migrated to GitLab and
|
|
The above shows 5 repositories that have been migrated to GitLab and
|
|
|
still active, two that should be migrated and archived. There's a
|
|
are still active, two that have be migrated and archived. There's a
|
|
|
third possible fate that is "destroy" in which case TPA will simply
|
|
third possible fate that is "destroy" in which case TPA will simply
|
|
|
mark the repository as inactive and will not migrate it.
|
|
mark the repository as inactive and will not migrate it.
|
|
|
|
|
|
|
|
See [issue tpo/tpa/team#41181](https://gitlab.torproject.org/tpo/tpa/team/-/issues/41181) for an example issue as well.
|
|
Note the verb tense matters here: if the repository is marked as
|
|
|
|
"migrated" or "archived", TPA will **assume the repository has already
|
|
|
|
been migrated and/or archived**! It is your responsibility to do that
|
|
|
|
migration, unless otherwise noted.
|
|
|
|
|
|
|
|
So if you *do* want TPA to actually migrate the repositories for you,
|
|
|
|
please make that explicit in the issue and use the proper verb tenses.
|
|
|
|
|
|
|
|
See [issue tpo/tpa/team#41181](https://gitlab.torproject.org/tpo/tpa/team/-/issues/41181) for an example issue as well,
|
|
|
|
although that one doesn't use the proper verb tenses
|
|
|
|
|
|
|
|
#### TPA part: lock down the repository and add redirections
|
|
#### TPA part: lock down the repository and add redirections
|
|
|
|
|
|
| ... | | ... | |
