since 20.04 is LTS, unless Breezy 3.1 is scheduled to be released soon, it seems this bug fixed should be backported to 3.0
my two cents
since 20.04 is LTS, unless Breezy 3.1 is scheduled to be released soon, it seems this bug fixed should be backported to 3.0
my two cents