On 2016-05-11 06:41:43 +0200, Salvatore Bonaccorso wrote: > Please see #823893 for why this has not yet seen as well an update in > unstable.
OK, but a decision should be made quickly. If 3.2.0 is not ready yet for unstable due to potential regressions, then a patched 3.1.2 should be uploaded to unstable (basically with the same as patch as stable, since the current version is exactly the same as the stable version before the security update). IMHO, this latter solution is probably better for testing; and if users see a regression in 3.2.0, they will be able to downgrade to the patched 3.1.2. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
