Missing 2017.2.0.post0 tarball
No description provided.
Comments (7)
-
-
OK, I didn't realise. Does it need to be
post0
or can I just update this tarball? -
reporter The tarball
2017.2.0.post0
has to be created from tag2017.2.0.post0
tag. No hacks please. -
In practice, just updating the tarball is "good enough". That was done for instant, fiat and dijitso, after some beta release tarballs had been uploaded in September. It looks a bit funny for people tracking the packages though (I had to relabel the instant, fiat and dijitso for Debian since I had already processed the September tarballs). Worse case scenario, it looks like fenics/bitbucket has been hacked.
Since there's already a precedent for the .post0 mechanism, used for dolfin, I'd recommend doing it that way (though it's not a huge drama if you just update the current tarball). Technically you could call it 2012.2.1, since it involves an update to the source code.
-
reporter Let's be consistent across released tags and tarballs.
-
Sensible policy. I'd forgotten about the tag.
-
- changed status to resolved
Chris has uploaded ffc-2017.2.0.post0.tar.gz, so we can close this issue now.
- Log in to comment
For context, the current 2017.2.0 tarball has .dev0 marked in ufc.h (i.e. marked as a beta release)