Comment 1 for bug 1331375

Are there any issues preventing chromium from being updated to a version without known security vulnerabilities? Even debian has v35 in stable-security since June 15, and Arch Linux (unsurprisingly) since June 11, and the vulnerabilites are public since June 10.

Since most other distributions (ignoring Fedora, which probably handles chromium in the sanest way…) have switched to v35 two weeks ago, the problems with the new version can't be that bad I guess. At least better than browsing with 4 CVEs. Or is this repeated chromium update delay due to a lack of manpower? In that case, is there any reason not to use and contribute to the debian packaging work directly?