Moving IREE Repository to the OpenXLA GitHub Organization

[Geoffrey Martin-Noble]

Hello all,

tl;dr: https://github.com/iree-org/iree will move to https://github.com/openxla/iree on or about 2023-02-20 at 14:00 PT. We will announce a precise time for the migration prior to executing it. You may need to update some links and there may be some brief infrastructure outages, but mostly everything should be auto-forwarded.

As previously announced, IREE is joining the OpenXLA project, an OSS ecosystem of ML compiler technologies. We've also mentioned that this will include the IREE repositories migrating to the OpenXLA GitHub organization. We're going to start with the main IREE repository at https://github.com/iree-org/iree and move it to https://github.com/openxla/iree. Other movement of repositories and potentially factoring out some shared components from IREE (infrastructure being a good candidate) will happen afterwards. I will be overseeing this migration and the aim is to make it as minimally disruptive as possible.

Those of you who were involved 6 months ago when we moved from the google GitHub organization to iree-org, may recall that there was some miscommunication with the team that manages the google org and the repository migration was triggered before we were quite ready for it. This time, we've got full control and have come up with a detailed testing plan, so hopefully there will be fewer hiccups (and you can blame me for anything that goes wrong 🙂). We also fortunately documented all the things that broke last time, so we can avoid hitting some of those same issues.

GitHub has relatively good tooling for moving a repository between organizations intact and does automatic forwarding of almost all requests (including fetching and cloning), but there are a few things that break. For those interested in the precise details, the full migration plan is documented in this GitHub issue and it will be updated with our progress. Please follow along there and raise any issues you come across. The basics are that we are going to create a copy of the IREE repository in the new organization first and test as much as possible there. We'll likely keep this repo private just to reduce confusion for those who may stumble across it.. When we've completed the testing, we'll delete the repo (since the name needs to be unused for the current repository to be moved) and announce the precise date and time of the migration. Currently the plan is to make the move on 2023-02-20 at about 14:00 PT.

If you have a dependency on the current repo location or any other technical concerns, please let us know on the GitHub issue. If you have any high-level feedback, please reply here or reach out to me directly.

Cheers,

Geoffrey

[Geoffrey Martin-Noble]

Testing has completed successfully and the migration will occur as scheduled 2023-02-20 at 14:00 PT

[Geoffrey Martin-Noble]

Apologies, I forgot to update the date in my earlier email after remembering the US holiday yesterday. The migration will be happening today, 2023-02-21 at 14:00 PT. I will send another announcement immediately before executing the GitHub repo move and then a final email when I complete the immediate steps following the migration that ensure all our infrastructure still functions. 

[Geoffrey Martin-Noble]

There was a brief delay while I fiddled with Project migration scripting. I am about to transfer the repository to the openxla organization. There may be some brief outages while things settle and I hotswap a few things.

[Geoffrey Martin-Noble]

The main part of the migration is complete. There will be some continued cleanup, but the repo is moved and CI and such should all be handling the new location. GitHub will auto-forward requests to the old URLs (except for docs, for which we have added a custom redirect), but you should probably update links you have saved (e.g. as git remotes) to the new location at your convenience. Anything doing textual matching (e.g. email filters) will need to be updated.

Please report any problems on the GitHub issue or if you need realtime assistance please mention me in the dedicated Discord thread (no SLO, but it will likely get my attention more quickly).

Thanks for bearing with us during this infra churn.

Cheers,

Geoffrey