Comment 20 for bug 1926062

> Declaring "Fix Committed" when a fix exists in an upstream tributary before anything has reached proposed is a procedure requested by seb128 and we now follow on the desktop team.

I'm not sure what you mean by "upstream tributary", but if the fix exists in the main Ubuntu packaging branch used by the desktop team (ie. Vcs-Git in debian/control points to it) then that makes sense, as it was in this case. If you mean it's just fixed upstream somewhere, then that doesn't make sense - Launchpad's bug tracker expects to have a separate task to track upstream status if you want that.

However, from an SRU perspective, I would expect an upload to the development release *before* an SRU is uploaded. Sometimes we make concessions (eg. during a development release freeze), but I don't think a sponsorship delay qualifies. The sponsor should be able to sponsor to the development release first, so there's no reason not to do it.

I see it's there now, but please could you adjust your processes to make sure that in the normal case, this happens? This would save me reviewing the SRU twice.