Please do not add the tarballs of the data to the actual (git version controlled) www repository of the website b/c git will download the full history (incl. all updated tar.gz files) when one clones the repository.
This way (depending on the compiler used of course) people trying out the gallery example can download the sample results and compare.
I believe the sample data tends to contain plot scripts etc as well, it would be great if the new downloads also contained all such extra material.
Roland, why should the data be replaced? Has it changed? I don't see a reason to replace the existing data if it hasn't changed. It is likely slightly different due to being run with a different compiler, machine, etc, but that is no reason to update the data.
We just uploaded the new data and updated the website.
@ianhinder the tarfiles each contain the date when they were created. No data is updated, instead it is added. The idea is to give a dataset that was produced with the current release. I do expect that there will be slight differences depending on compiler etc. I would rather have a dataset that documents "this was the data that the person who claimed to have run the test saw" rather than having the data slowly drift away from the data produced by the newest compiler on the newest machine with the newest release. The tarballs are all kept here: https://bitbucket.org/einsteintoolkit/www/downloads/ I see no harm (other than using space on btibucket's servers) in updating the data files so updating them would seem the less troublesome option.