Thanks a lot jibel for looking at it again.
AFAUI, distro-info-data will be outdated during a new release set up and all the other times it should be up-to-date. By using 'distro_info.UbuntuDistroInfo().devel()' the new release will be picked up once distro-info-data is updated. If we want to have a config file for this purpose, that will need to be modified manually anyway during the start of a release. I do not there fore see an advantage. But I could miss anything here, for e.g. this failure itself is going to be in the way of registering a new release and releasing new distro-info version.
Thanks a lot jibel for looking at it again. info.UbuntuDist roInfo( ).devel( )' the new release will be picked up once distro-info-data is updated. If we want to have a config file for this purpose, that will need to be modified manually anyway during the start of a release. I do not there fore see an advantage. But I could miss anything here, for e.g. this failure itself is going to be in the way of registering a new release and releasing new distro-info version.
AFAUI, distro-info-data will be outdated during a new release set up and all the other times it should be up-to-date. By using 'distro_