I don't think that having a separate news feed for the Windows
binaries/packages is appropriate, since these are just builds of
the source packages announced in the php.net release news feed.
Instead we could add one (or multiple) links to the php.net
release news feed pointing to the Windows builds (which would
require to have permanent links, though, i.e. we should no longer
move files to archives/ if new releases are available).

A file with machine readable information regarding available
releases/snaps etc. would make sense, though.  Allowing access to
cache.info[1] might be a start.

[1] <https://windows.php.net/downloads/releases/cache.info>

Since downloads are offered on two different domains, I suggested a separate feed. However, adding to the php.net news feed is fine with me, if that causes no other issues and the various windows versions (x86/x64, TS/NTS) are somehow detectable.

@cmb it's not about a news feed, i think. There's no request to issue separate release announcements or alike. It's merely about making the listings machine readable. That could be done by generating some JSON, similar how it is already done for snapshots, but including also archive releases. There might be a separate implementation for this as a cronjob, similar what is done for the snaps. We should not change the folder structure there, as it will sure break some users.

It is sure a chunk of work, but it would be sure useful for everyone and @arueckauer was willing to contribute it. We should just figure out what exactly were to do. Imo adding to the php.net feed would be not very useful, as the information will need to be maintained twice at different places. For PECL, it already needs to be maintained at two places, but there's no good choice there. It is easier to integrate it on windows.php.net somehow, so it generates some releases.json. If we wanted, that could be also extended to the pecl releases.

Thanks.

Is there any way I can contribute to a solution on this issue?

> Is there any way I can contribute to a solution on this issue?

Yes, sure; that would be very welcome!

The source code of windows.php.net is publicly available[1], and
although it requires quite some tweaks to be run locally, you may
be able to provide a PR[2] which also would provide a better
discussion environment than this bug tracker. :)

[1] <http://git.php.net/?p=web/windows.git;a=summary>
    <https://github.com/php/web-windows>
[2] <https://github.com/php/web-windows/pulls>

This has been resolved quite some time ago; there are now
release.json files available, e.g.
<https://windows.php.net/downloads/releases/releases.json>