[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Automating the downloads web page

From: Julian Foad <julianfoad_at_apache.org>
Date: Fri, 25 Oct 2019 14:45:01 +0100

Nathan Hartman wrote:
> Julian Foad wrote:
>> How can we best insert this into 'downloads.html', at the right place?
> Various [tools...] insert their generated code between special comments.

I'd like something more standardized.

We already use 'ezt' templating here. One option would be to generate
'download.html' from 'download.html.ezt' which would contain

<h3>Latest regular release ...
[ezt templating here which generates this content]

<h3>Supported LTS releases ...
[ezt templating here which generates this content]

<h3>Pre-releases ...
[ezt templating here which generates this content]

The generator would have to know how to obtain a list of all the svn
versions that are currently to be listed for download, along with their
relevant details (release status, filenames, links, checksums, etc.).

That list should then be defined in some new, machine readable data
source -- perhaps a JSON or YaML file under version control. Until now,
the canonical version of that list has been "whatever is shown in
download.html". Changing to use a canonical source data file would be a
good thing.

That's the sort of thing I'd like to do.

There's a similar but much simpler issue with updating the 'news': we
copy the same news items into both 'news.html' and 'index.html', and
manually prune the list in 'index.html' to have approximately 3 entries.
  That's not a lot of manual work but it's lame. We should have a
separate, struxtured, storage location for each news item and then an
automatic way of pulling and formatting the newest 3 of them into
'index.html' and all of them into 'news.html'.

- Julian
Received on 2019-10-25 15:45:03 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.