[tsc-devel] Re-releasing 2.0.0 as 2.0.1?

Quintus | Sun, 11 Oct 2015 08:52:56 UTC

Hi everyone,

in the course of investigating ticket #452, the root cause of the
problem appears to be that the 2.0.0 windows binary on our FTP is
corrupt. Three people have now confirmed that a new binary that I built
from the same code does not expose the problem, so I guess we can fairly
assume that the win32 installer got damaged during upload or otherwise.

The question now is about how to proceed. There are two possibilities.

1. Replace the faulty 2.0.0 win32 installer binary on our FTP, and post
   a notice to the website that it was corrupt.
2. Re-release the very same code as 2.0.1 and list rebuilding of the
   binary as the only change.

I’m more in favour of option 1, but datahead seems to be more in favour
of option 2. I’d be okay with either, but let me know what you think.

Valete,
Quintus

-- 
#!/sbin/quintus
Blog: http://www.guelkerdev.de

GnuPG key: F1D8799FBCC8BC4F