I think you misunderstand me. A backport via the backports pocket (feature updates that are opt in for users) is fine. But we can also ship a backport via the updates pocket (updates that are recommended for automatic upgrade by users). In this case it looks like it'll meet the stricter requirements of the updates pocket as it'd a bugfix-only backport.
My point was that you can't do a "sync"; you have to do a "backport" of the package (by adding another changelog entry with a bug reference etc) and get that sponsored/uploaded in order for me (in the SRU team) to be able to accept it. This is distinct from the backports process, which is a separate process to provide opt-in feature enhancements.
I think you misunderstand me. A backport via the backports pocket (feature updates that are opt in for users) is fine. But we can also ship a backport via the updates pocket (updates that are recommended for automatic upgrade by users). In this case it looks like it'll meet the stricter requirements of the updates pocket as it'd a bugfix-only backport.
My point was that you can't do a "sync"; you have to do a "backport" of the package (by adding another changelog entry with a bug reference etc) and get that sponsored/uploaded in order for me (in the SRU team) to be able to accept it. This is distinct from the backports process, which is a separate process to provide opt-in feature enhancements.