<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Le 2015-12-11 23:43, Satish Balay a
écrit :<br>
</div>
<blockquote cite="mid:alpine.LFD.2.20.1512112237430.3266@asterix"
type="cite">
<pre wrap="">
We do autmoatically generate tarballs everynight - its avaliable at:
<a class="moz-txt-link-freetext" href="http://ftp.mcs.anl.gov/pub/petsc/petsc-master.tar.gz">http://ftp.mcs.anl.gov/pub/petsc/petsc-master.tar.gz</a> [but we don't
maintain snapshots - i.e old tarballs for this]
</pre>
</blockquote>
interesting! I didn't knew that... Then maybe creating a tarball
for the "maint" branch and naming it with the date (or the sha), and
then making it available on the "Download" page would be a more easy
thing to do?<br>
<br>
How "far" or different is the master branch from the maint branch
right now? I see <a class="hash execute"
href="https://bitbucket.org/petsc/petsc/commits/3f7bb316d2abd318f1cc7393382d1a7d22094d25?at=maint">3f7bb31</a>
in maint but it is not clear (in bitbucket) if it is in master...?<br>
<br>
<blockquote cite="mid:alpine.LFD.2.20.1512112237430.3266@asterix"
type="cite">
<pre wrap="">
However adding in 'release' strings is a manual process - so we do
this at the release time. [so we would have to do this stuff for rc]
Here is a counter argument against this proposal. For folks interested
in RC - could consider [for eg] 3.6.0 as RC - and test it out - and
have all the issues discovered by 3.6.1. But this usually doesn't
hapeen [and we have 3.6.1, 3.6.2, 3.6.3, 3.6.4 etc..]
Also testing against master would catch issues early on - and not wait
until the rc/release..
</pre>
</blockquote>
Yep, but isn't Petsc master far away from maint?<br>
<br>
Thanks!<br>
<br>
Eric<br>
<br>
ps: there is a typo here at the bottom
(<a class="moz-txt-link-freetext" href="http://www.mcs.anl.gov/petsc/developers/">http://www.mcs.anl.gov/petsc/developers/</a>):<br>
<br>
"The nightly tarball ... the doumentation built. ..."<br>
<br>
</body>
</html>