On Tue, Feb 11, 2020 at 9:20 PM Fabiano Fidêncio <fiden...@redhat.com> wrote:
> Christian, > > On Tue, Feb 11, 2020 at 4:55 PM Christian Ehrhardt > <christian.ehrha...@canonical.com> wrote: > > > > Hi, > > for some recent releases the new ubuntu version was added after the > version > > was released. Which made it odd for users to not find the version they > are on. > > This time lets add 20.04 ahead of time. > > > > Since there isn't a released versions yet the links will have to go to > the > > daily builds. Those are and will continue to be correct and more > up-to-date > > than the release images. But obviously e.g. Volume-size will change. > > > > I have added the expected final URLs in the XML so that you should have > an > > easy switch after the release in case you want to switch to the release > URLs. > > > > While I was working on that I found some more fixups that could be > applied. > > > > Cool, I'll review these patches Tomorrow. Meanwhile, I'd like to > mention that the preferred way to submit patches for libosinfo > projects is opening a Merge Request against > https://gitlab.com/libosinfo/. > > Would you mind opening the MR there? If you do mind, I'll review the > patches here in the ML. > No problem at all, but that will add another patch to the readme :-) Because I only submitted it here as-is because it said: "Patch submissions are welcomed from any interested contributor. Please use the libosinfo list as the preferred way for patch submissions, or discussions about the code: https://www.redhat.com/mailman/listinfo/libosinfo " I'm more than happy to use the gitlab MR workflow on this. => https://gitlab.com/libosinfo/osinfo-db/-/merge_requests/90 Best Regards, > -- > Fabiano Fidêncio > > -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd
