DevHeads.net

Req #78140 [NEW]: List available releases as Feed (windows.php.net)

Operating system:
PHP version: Irrelevant
Package: Website problem
Bug Type: Feature/Change Request
Bug description:List available releases as Feed (windows.php.net)

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

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

As recommended by Anatol Belski (@weltling) (see
<a href="https://twitter.com/weltling/status/1136962886386036736" title="https://twitter.com/weltling/status/1136962886386036736">https://twitter.com/weltling/status/1136962886386036736</a>) 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.

Comments

Req #78140 [Opn]: List available releases as Fee

By Christoph Micha... at 08/06/2019 - 13:10

Edit report at <a href="https://bugs.php.net/bug.php?id=78140&amp;edit=1" title="https://bugs.php.net/bug.php?id=78140&amp;edit=1">https://bugs.php.net/bug.php?id=78140&amp;edit=1</a>

ID: 78140
Updated by: <a href="mailto: ... at php dot net"> ... at php dot net</a>
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:

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>

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

@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.

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.

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>

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

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

As recommended by Anatol Belski (@weltling) (see <a href="https://twitter.com/weltling/status/1136962886386036736" title="https://twitter.com/weltling/status/1136962886386036736">https://twitter.com/weltling/status/1136962886386036736</a>) 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.

Req #78140 [Com]: List available releases as Fee

By tim dot slot at... at 08/06/2019 - 12:39

Edit report at <a href="https://bugs.php.net/bug.php?id=78140&amp;edit=1" title="https://bugs.php.net/bug.php?id=78140&amp;edit=1">https://bugs.php.net/bug.php?id=78140&amp;edit=1</a>

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:

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

Previous Comments:
@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.

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.

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>

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

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

As recommended by Anatol Belski (@weltling) (see <a href="https://twitter.com/weltling/status/1136962886386036736" title="https://twitter.com/weltling/status/1136962886386036736">https://twitter.com/weltling/status/1136962886386036736</a>) 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.

Req #78140 [Opn]: List available releases as Fee

By Anatoliy Belsky at 06/13/2019 - 16:33

Edit report at <a href="https://bugs.php.net/bug.php?id=78140&amp;edit=1" title="https://bugs.php.net/bug.php?id=78140&amp;edit=1">https://bugs.php.net/bug.php?id=78140&amp;edit=1</a>

ID: 78140
Updated by: <a href="mailto: ... at php dot net"> ... at php dot net</a>
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:

@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.

Previous Comments:
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.

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>

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

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

As recommended by Anatol Belski (@weltling) (see <a href="https://twitter.com/weltling/status/1136962886386036736" title="https://twitter.com/weltling/status/1136962886386036736">https://twitter.com/weltling/status/1136962886386036736</a>) 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.

Req #78140 [Com]: List available releases as Fee

By tim dot slot at... at 06/11/2019 - 10:32

Edit report at <a href="https://bugs.php.net/bug.php?id=78140&amp;edit=1" title="https://bugs.php.net/bug.php?id=78140&amp;edit=1">https://bugs.php.net/bug.php?id=78140&amp;edit=1</a>

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:
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>

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

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

As recommended by Anatol Belski (@weltling) (see <a href="https://twitter.com/weltling/status/1136962886386036736" title="https://twitter.com/weltling/status/1136962886386036736">https://twitter.com/weltling/status/1136962886386036736</a>) 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.

Req #78140 [Opn]: List available releases as Fee

By Christoph Micha... at 06/11/2019 - 08:52

Edit report at <a href="https://bugs.php.net/bug.php?id=78140&amp;edit=1" title="https://bugs.php.net/bug.php?id=78140&amp;edit=1">https://bugs.php.net/bug.php?id=78140&amp;edit=1</a>

ID: 78140
Updated by: <a href="mailto: ... at php dot net"> ... at php dot net</a>
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:

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>

Previous Comments:
Description:
windows.php.net currently offers no other way of listing available releases, archives and latest versions other than the "directory listing" HTML (see <a href="https://windows.php.net/downloads/releases/" title="https://windows.php.net/downloads/releases/">https://windows.php.net/downloads/releases/</a>).

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

As recommended by Anatol Belski (@weltling) (see <a href="https://twitter.com/weltling/status/1136962886386036736" title="https://twitter.com/weltling/status/1136962886386036736">https://twitter.com/weltling/status/1136962886386036736</a>) 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.