Many releases are missing from that data.
Today, if someone forgets to add a release to our webpage, we can easily
fix that later on by editing that page and adding an old release. Is
that possible with the reporter, too?
Or in other words, todays release page is very easy to maintain - and
for a release you have to edit the downloads page anyway. At first look,
relying on the reporter data seems to be more complicated.
Carsten
On 04.05.2020 16:04, Bertrand Delacretaz wrote:
On Mon, May 4, 2020 at 3:56 PM Bertrand Delacretaz
<[email protected]> wrote:
...It looks like that reporter website belongs to
http://community.apache.org/, I'll ask there if that releases data or
page could be made public...
turns out that the release data itself is already public,
https://svn.apache.org/repos/asf/comdev/reporter.apache.org/trunk/data/releases/sling.json
I'll look at how to merge that automatically in
https://sling.apache.org/releases.html , we already have some similar
processing in the website for [1]
-Bertrand
[1]
https://github.com/apache/sling-site/blob/master/src/main/jbake/templates/repolist.tpl
--
--
Carsten Ziegeler
Adobe Research Switzerland
[email protected]
