Comment 7 for bug 1730927

> Reading the wiki page on stable release updates[1] I see no option to get this in artful. As described in section 3, the version fixing the bug has to be tested in dev before - the problem now is that dev has 1.7.2-2 while artful has 1.6-1 thus it's not possible to test a version in dev that only fixes this bug - and bumping the version in artful is not acceptable.

There is no requirement to "test a version in dev that only fixes this bug". The spirit of the rule you refer to is that 1) you do not fix the bug in the stable release but not in the development release so that when they upgrade to the next release they will regress; and that 2) you do not use the stable release as an experimentation platform for learning about the bug.

As an SRU team member I'm happy to make it clear that a fix to Artful to match Twitter's limit is acceptable (in my view) under the "...changes in the environment, server protocols, web services..." part of the SRU policy.

The fix itself needs to have minimal regression risk, etc. A minimal cherry-pick would be ideal. And of course someone needs to volunteer and drive the landing of this fix (follow SRU procedure, etc).