Renaming scikit-hep/awkward-1.0 → scikit-hep/awkward

[jpivarski]

I plan to rename the repo because later this year it won't be version 1 anymore (already isn't 1.0). The names "scikit-hep/awkward-array" and "scikit-hep/awkward-0.x" are already taken by the 0.x legacy project and so a natural next choice is "scikit-hep/awkward". This would also make it the same as the package's PyPI/conda name. GitHub will automatically redirect the old name to the new name (forever).

I've mentioned this a few times with no response (e.g. on Gitter), so I assume it's uncontroversial. I just want to give everyone fair warning that it's happening tomorrow, May 5, 2022, less than an hour after 8:00am U.S. Central == 15:00 CERN. (I was going to do it now, then realized that I should probably give an exact time with enough warning for people to see it during the workday in Europe.) No PRs will be merged between now and then (i.e. the next PR merge will be after the repo has a new name). Awkward 1.9.0rc3 represents the state of the repo immediately before the name-change and 1.9.0rc4 will be immediately after the name-change, with only as many changes to the repo as are needed to accommodate (probably none, just VERSION_INFO).

Most likely, no one will need to change anything. Personally, I'm going to git clone a new copy of the repo after the change with the new name, just in case. Eventually, we should also change links so that they don't have to redirect, but that's not a high priority.

[jpivarski]

@lgray @nsmith-

[henryiii]

git remote set-url origin [email protected]:scikit-hep/awkward will keep your local branches and stashes intact if anyone wants to do that.

[jpivarski]

This was on Slack, but anyway: @ianna, @ioanaif, @agoose77, @swishdiff, @aryan26roy, @martindurant, @douglasdavis (for the exact date/time).

[jpivarski]

It's done!

GitHub redirects everything automatically, and the GitHub Actions continued to work after the change. Azure had to be set up again because it refused to follow the HTTP redirect. (The error message acknowledged that it's a redirect link, but just failed instead of following it.)

All of that has been set up again. The test of CI is in scikit-hep/awkward#1448 and the test of CD is release 1.9.0rc4. Everything seems to have triggered, and we'll know in about 4 hours (ARM is slow to build) whether everything works. I don't expect any problems.

There had also been some CI tests that weren't marked "required." That was an oversight, and I fixed that.

I should also check https://github.com/conda-forge/awkward-feedstock to be sure that deployment to conda-forge is also working, but it looks like it only updates for non-pre-releases. I might have to deploy a 1.9.0 for that.