build-image: use latest instead of unstable by default
This is actually a question: storage.puri.sm which is used when not using "latest", seems to be offline, so why not make "latest" default and clean up or fix later?
This is actually a question: storage.puri.sm which is used when not using "latest", seems to be offline, so why not make "latest" default and clean up or fix later?