QA

I think that the quality assurance is pretty good. We're building the test suite up from a minimal one from years back to a really solid one, and you and Bill are very responsive to bug reports.

Charles Greathouse
Analyst/Programmer
Case Western Reserve University

On Mon, May 12, 2014 at 8:15 AM, Karim Belabas <Karim.Belabas@math.u-bordeaux.fr> wrote:

* Georgi Guninski [2014-05-12 13:36]:

> As of now yesterday's bugs appears fixed in master.
>
> You might consider improving your
> quality assurance process ;)

That's the whole point of the 'master' (aka testing branch). From the FAQ:

"nothing is guaranteed, although everything usually works. Large sections of
code are modified, features appear or are cancelled, interfaces change
according to the feedback we receive, many bugs are fixed and new ones sneak
in. Eventually, the testing version coalesces into a stable one, and a new
testing branch is started."

Wrt quality assurance, we do what we can: support on mailing lists & private
mail, public bug tracking system, continuous integration with public benches
& code coverage analysis, etc. I'm open to suggestions bearing in mind
the paucity of ressources (the equivalent of 2 full-time developpers, say,
for everything PARI-related).

Right now we're developping lots of new features (and about ten branches are
currently waiting for a merge), which means less time for testing and quality
assurance.

Thanks for submitting bug reports ! :-)

Cheers,

K.B.
--
Karim Belabas, IMB (UMR 5251) Tel: (+33) (0)5 40 00 26 17
Universite Bordeaux 1 Fax: (+33) (0)5 40 00 69 50
351, cours de la Liberation http://www.math.u-bordeaux1.fr/~kbelabas/
F-33405 Talence (France) http://pari.math.u-bordeaux1.fr/ [PARI/GP]
`