CCing myself. When this is fixed we can update https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB to link to it instead of the github releases page.

You mean having something like https://getfedora.org/fmw/FedoraMediaWriter-osx-latest.dmg which points to the latest release version?

Actually the binaries are build by releng and synched directly to the web production server, sundries01, and not stored in the web repo. We could think about a redirect to the latest version, but this is more an Infra issue rather than web. Maybe Patrick or Kevin have some ideas how to get this redirect work as automated as possible.

Yes, exactly that.

Perhaps we could do something like was done for the two week atomic latest?

https://pagure.io/fedora-websites/pull-request/43 ?

Or it would be nice if all of them used the same methods...

:salad:

Yikes, I don't really like that PR, but for reasons that aren't entirely relevant here. I don't think we can really use the 'same method' for locating the latest mediawriter binaries as we use for locating compose artifacts (use fedfind! always use fedfind!), because mediawriter binaries aren't compose artifacts, so we can't rely on stuff like the compose metadata, fedmsgs that are emitted when composes happen, PDC queries, etc. Note how heavily that code relies on globalvar.release['curr_id'], which is (presumably) the compose ID of the 'current' two-week Atomic stable compose.

@kevin do you have any other ideas here?
It would be just for the wiki I guess, because websites can't use that latest image, because FMW is pointing to the release.json. We could use it only for download purposes instead of updating it at every new release.

We have an easy workflow for that now, although we need a ticket when a new version of FMW has been built an uploaded to the server.
I'm going to close this issue as wontfix for the websites team, eventually we can set up a redirect the same way as we did for Cloud images time ago, but that's an Infra task.