Project: datamanagement
Issue DM-3780: Rationalize lsst/xrootd repo and maintenance procedures
The procedure for pulling/pushing xrootd changes from/to the upstream official xrootd repo is cumbersome, confusing, and error-prone. Buildbot now has support for releasing packages from branches other than master. Given this, we can now reasonably replace our lsst/xrootd repo with a fresh genuine fork (shared history) of upstream, then carry our lsst-specific work forward on a dev-branch. This will make it much easier to track and contribute to the xrootd project moving forward. Existing legacy branches and tags are to be migrated to the fresh fork, so historical builds will not be broken.
Story points: 1