Edit report at https://bugs.php.net/bug.php?id=78140&edit=1

 ID:                 78140
 Comment by:         arueckauer at gmail dot com
 Reported by:        arueckauer at gmail dot com
 Summary:            List available releases as Feed (windows.php.net)
 Status:             Open
 Type:               Feature/Change Request
 Package:            Website problem
 PHP Version:        Irrelevant
 Block user comment: N
 Private report:     N

 New Comment:

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.


Previous Comments:
------------------------------------------------------------------------
[2019-06-11 12:52:16] [email protected]

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>

------------------------------------------------------------------------
[2019-06-11 09:14:02] arueckauer at gmail dot com

Description:
------------
This feature requests is releated to windows.php.net only (www.php.net has this 
feature already implemented).

windows.php.net currently offers no other way of listing available releases, 
archives and latest versions other than the "directory listing" HTML (see 
https://windows.php.net/downloads/releases/).

It would be a great feature to have a XML feeds (like 
https://www.php.net/releases/feed.php), JSON or possible other formats.

As recommended by Anatol Belski (@weltling) (see 
https://twitter.com/weltling/status/1136962886386036736) I am opening this 
ticket for discussion. I would be happy to help on the implementation, but have 
no experience so far pertaining to the PHP website itself.



------------------------------------------------------------------------



--
Edit this bug report at https://bugs.php.net/bug.php?id=78140&edit=1

-- 
PHP Webmaster List Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to