<html>#2673: provide (historical) tar archives for each Cactus release
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>task</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td>EinsteinToolkit website</td></tr>
</table>
<p>A while ago in a ET call we concluded that it would be good to provide tar files of a full ET checkout (no version control metadata) for each release. This is useful in case repository servers referred to in thornlists go away.</p>
<p>Roland has copies of most releases and should be able to provide tar files.</p>
<p>For upcoming release we could also include the tar files as downloadable “deposits” in the Zenodo publication <a data-is-external-link="true" href="https://doi.org/10.5281/zenodo.3350841" rel="nofollow">https://doi.org/10.5281/zenodo.3350841</a> This is nice to have an external hoster that should be around for a long time, but adds extra complications for the release process since one must create the tarball-to-be-deposited (incl. einsteintoolkit.bib which points to the Zenodo entry) before the release and before the Zenodo entry is published (similar to Description.md).</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2673/provide-historical-tar-archives-for-each'>https://bitbucket.org/einsteintoolkit/tickets/issues/2673/provide-historical-tar-archives-for-each</a></p>
</html>