7 Nov
2013
7 Nov
'13
9:42 a.m.
On 07.11.2013 11:40, Antony Polukhin wrote:
+1 IMO, fussily adding support for suddenly released (and untested during development stage) compilers is not what must be done during the final release stage. I would propose fixing the compile-time bugs with VC12. Then, users will be able to test the 1.55.0 with their code and find the runtime bugs.
May be a better solution would be to release a 1.56 sooner with less new features but with fixes for msvc-12.0?
If there was no git migration, I would suggest releasing 1.55.1 with "experimental" VC12 support. -- Sergey Cheban