Ok, after browsing through the news and thinking about it, I feel that this could potentially be SRUable. My rationale would be: the package is in main and typically an all-or-nothing package, where we can't cherry pick single pieces easily. So to keep our users up-to-date, there's no other choice but including a new upstream release.
Anyway, with my SRU hat on, I'm giving a +1 on getting this in. But as with any risky bits like this, I'd appreciate if we could keep the package in -proposed for a bit longer and, possibly, organizing a call-for-testing for it.
Ok, after browsing through the news and thinking about it, I feel that this could potentially be SRUable. My rationale would be: the package is in main and typically an all-or-nothing package, where we can't cherry pick single pieces easily. So to keep our users up-to-date, there's no other choice but including a new upstream release.
Anyway, with my SRU hat on, I'm giving a +1 on getting this in. But as with any risky bits like this, I'd appreciate if we could keep the package in -proposed for a bit longer and, possibly, organizing a call-for-testing for it.