Hi Gregor and list, On 04/05/2023 08:25, Gregor Jasny wrote: > Hello Mauro and list > > On 21.03.23 22:21, Mauro Carvalho Chehab wrote: >> Gregor Jasny <gjasny@xxxxxxxxxxxxxx> escreveu: >>> I'm happy to announce that v4l-utils 1.24.0 has been released. This will >>> be the last version before the build system will be migrated from >>> Autotools to Meson. >>> > >> I wouldn't mind if we would have a shorter release time for version >> 1.26 - or maybe it is time to increase major, so version 2.0. >> >> As we are now using a new building system, it would be nice to have >> a stable version frozen, with not much other changes, in order >> to allow distros to opt either to use version 1.24 with autotools >> or to migrate to the newest version, with meson, but not many other >> changes. >> >> So, perhaps we should aim release a new version in 2 months or >> so, once we have enough time to do cleanups if needed and having >> media maintainers and developers familiar with the new way. > > It looks like the dust after the meson migration has been settled. When would be a good time for a new v4l-utils release? I'm available this weekend or the upcoming ones. > > Is there anything you'd like to land in the mainline branch prior to a new release? Actually, there is one thing I want to discuss. I maintain the edid-decode utility (https://git.linuxtv.org/edid-decode.git/) and I have received several request for 'a proper version number' and releasing it as a package. I have been wondering whether this utility shouldn't be moved to v4l-utils so it is part of the v4l-utils release mechanism. Since V4L2 also deals with setting/getting EDIDs it is not unreasonable. Would there be any objections if I did that? If there are no objections, then it would be nice to include this in a new release. Regards, Hans
