Proposed changes to how images are names and tagged about docker-images HOT 3 OPEN

The aarch64 cross compiler image might be named aarch64-bionic, and the raspbian one raspbian10, to match the cross compiler image targets? But they are not specifically for jetson and frcvision (which has been renamed to wpilibpi in any case). A binary built with the raspbian10 cross compiler will work on any raspbian10-based image, not just wpilibpi.

from docker-images.

I am fine changing the names for those containers, but I am hesitant to put a version in the name. Both of which will be reaching end-of-life (Buster August 2022, Bionic April 2023). Plus, binaries built on a raspbian10 container should be compatible with raspbian11. I believe having a container called wpilibpi that is tagged for the current WPILib release makes it clear that it is for the WPILib rPI image that was released for the season.

The Jetson is an odd case because there is not a WPILib branded image that I am aware of. Preferably, I want to see what PhotonVision will come up with, as I have heard that they are looking into building a Debian based distro for it.

from docker-images.

These images are basically just images for cross-compilation to the particular target (with the cross compiler preinstalled). We use them primarily for building binary artifacts for that (generic) target; it doesn't matter whether the target is wpilib branded or not.

from docker-images.