On Wed, May 8, 2024 at 11:25 PM Sven Schreiber <sven.schreiber(a)fu-berlin.de>
wrote:
Am 08.05.2024 um 23:08 schrieb Cottrell, Allin:
On Wed, May 8, 2024 at 3:58 PM Sven Schreiber<sven.schreiber(a)fu-berlin.de>
<sven.schreiber(a)fu-berlin.de> wrote:
Agreed, this needs to be fixed in the package. However, from the
timeline of the release of gretl 2024a on April 5th, it would mean that
the package should have failed already in the run-up to the release. My
question then is, why didn't we notice? I thought it's a standard part
of the testing parcours to check the sample scripts of all packages.
You're right. I'm afraid there was a testing failure in this case. All
the gfns had been tested probably a day before the March 29 change,
and at the time it didn't seem that anything "significant" had changed
between then and the April 5 release. But that's a risky assumption,
and not one I'll make in future. Obviously, it would be good if I were
not the only person testing all the gfns' sample scripts in the run-up
to a release.
Yes, we should better distribute those tasks.
thanks
sven
_______________________________________________
Gretl-devel mailing list -- gretl-devel(a)gretlml.univpm.it
To unsubscribe send an email to gretl-devel-leave(a)gretlml.univpm.it
Website:
https://gretlml.univpm.it/postorius/lists/gretl-devel.gretlml.univpm.it/