fedfind 2.7 contains various fixes to fedfind, python-wikitcms and relval related to how the GA milestone name for Fedora changed from 'Final' to 'RC' with the switch to Pungi 4 (so, for Fedora 24 onwards). This had various consequences mainly for all the CLIs; all the automated stuff tends to use compose IDs and labels which mostly weren't affected by this, but the CLIs all had issues with it. fedfind images could not find RC composes, relval size-check could not check image sizes for them, relval report-results could not report results for an RC compose besides the auto-detected current one, etc.

The update also contains a couple of other fixes for relval size-check: it now properly catches the case where it couldn't find any images for a variant, and it includes the arch in the comment for oversized images (so we can tell which image is actually oversize when the same image exists for multiple arches).

fedfind 3.0 changes how fedfind finds images for composes without metadata (which is basically milestone - Alpha / Beta - and stable releases). Formerly it found them by scraping rsync output, which was slow, generated quite a lot of load on both server and client, and was vulnerable to the rsync server being full. We have now tweaked things so that the primary mirror has imagelist files for the fedora, alt and archive trees which list every single image file - but no other files - in those trees. fedfind now simply parses these imagelist files to find images.

As the files only list images they are pretty small (the biggest is under 500KiB) and they are cached locally and only re-downloaded when they change, this is much faster, more efficient, and uses less bandwidth.

There are also some changes to ensure the tests run properly on EL 6, EL 7 and Fedora 23, and a missing dependency for EL 6 was added - argparse is a part of the Python standard library for all the other distros, but for EL 6 it is still a separate package.

fedfind 3.1 changes how fedfind handles metadata for composes which were originally created by Pungi 4 and had real metadata, but were then modified in some ways and had their metadata removed. This includes milestone and stable releases for Fedora 24 and later: when these are placed in their 'final' locations on the mirrors, some contents are split into different locations and some deliverables are removed. Previously, fedfind would simply synthesize metadata for these composes, as it does for pre-Pungi 4 composes. Now, it first attempts to find the original metadata (from PDC) and adjust it for the modified image locations, while preserving all the other image attributes from the original metadata (including ones it could not synthesize). It will only fall back to synthesizing the metadata if it cannot find corresponding metadata from PDC. The practical result of this is that you should get more reliable and complete metadata for these composes.