> They are still, what the name suggests: candidates, with no confirmation > to be useful in a production environment. I don't see why they should > ever migrate to testing (as they did in 1.11.1rc.1). Last time, we had > an numpy RC in testing for more than four months (2016-05-06 to > 2016-10-16)! This doesn't confirm a sigh quality tendency. And imagine
this is the diff between 1.11.2rc1 and 1.11.2 (not the same versions you mentioned, but the most recent one we can make such comparison): https://anonscm.debian.org/cgit/python-modules/packages/python-numpy.git/diff/?h=upstream/11.11.2 the version is just a name, there will be bugs even in the most shiny new release of every software > that happens now; chances are high that we release Stretch with a numpy > release candidate. > > IMO the way numpy changes are to be tested in Debian needs some adjustment. -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi