Add focal to list of distros

[sloretz]

Mimicking #51

I'm not 100% sure this is still relevant since it sounds like this is a prerequisite to create a focal bootstrap repo #51 (comment), but one already exists.

[tfoote]

The new bootstrap repository is based on the aptly toolchain and is not using reprepro-updater.
@nuclearsandwich would know better but I think that this branch 'master' is now deprecated fully where the bootstrap repo was the last element using it not the refactor branch.

[sloretz]

The new bootstrap repository is based on the aptly toolchain and is not using reprepro-updater.
@nuclearsandwich would know better but I think that this branch 'master' is now deprecated fully where the bootstrap repo was the last element using it not the refactor branch.

@tfoote @nuclearsandwich Sounds like I can assume this repo is deprecated and the PR is not needed then. Closing.

[nuclearsandwich]

I wanted to check the math on the conclusion here.

This repository contains scripts wrapping reprepro which are still in use on the buildfarm_deployment repository host. The "refactor" branch is in use. (buildfarm_deployment source).

The overall reprepro updater configuration which governs what repositories to set up and signing keys and whatnot is taken from the buildfarm_deployment_config (public example config entry)

ros_buildfarm has an import_upstream job. The default configuration uses the ros_bootstrap.yml also from the buildfarm_deployment_config. (public example config entry)

The config files in this repository for importing from various upstreams are technically usable from the import_upstream job but doing so is quite opaque, especially to people setting up buildfarm replicas. I think at this point we've settled on importing everything into the aptly-backed bootstrap repository and using the import_upstream job to get whatever's in that to the ROS and ROS 2 repositories.

[tfoote]

My conclusion was that master was deprecated. We're still using refactor branch. Though we could consider moving the wrapper scripts into the buildfarm now as that's the only think we're using these days and we've already got lots of wrapper scripts in ros_buildfarm there's not a real need for them to be in a separate repository.

As we're switching to the new repository management tool we should find a way to document and track those packages natively in their old home instead of trying to maintain these rules that we can't/won't ever execute.