On Fri, Dec 07, 2007 at 11:56:21AM +0100, Riccardo (Jack) Lucchetti wrote:
Since 1) is a potentially disruptive bug, I'd like to propose a bugfix
release as soon as possible, fixing 4) as far as possible.
Opinions?
If the bugfix release is taking more than a few days to go out, maybe it's worth
to post a warning message about 1) on the gretl-announce ML (provided you have
the power to do it).
On the long term, it would be nice to have some kind of regression[1] test suite
to identify such problems before releasing; don't know if the NIST test will do,
maybe we need a carefully crafted gretl script.
Cri
[1] Of course I mean both software engineering regressions and econometric regressions :)
--
GPG/PGP Key-Id 0x943A5F0E -
http://www.linux.it/~cri/cri.asc
Free software, free society -
http://www.fsfeurope.org