I suppose that a mass-change from Fix Committed to Fix Released, at release time, would be infeasible even if mass changes were implemented in Launchpad. For example, when NoMoreSourcePackages lets bugs be fixed on a mainline during a release's code freeze, not all bugs that happen to be Fix Committed on release day will have their fixes included in the release, and determining the subset that have been included would be too much work (as prefigured by the current dearth of distrorelease bug targeting you mentioned).
I'm unclear about whether you think there is a *useful* distinction between "Fix Committed" and "Fix Released" at all. If so, how would the distinction help in daily work?
I suppose that a mass-change from Fix Committed to Fix Released, at release time, would be infeasible even if mass changes were implemented in Launchpad. For example, when NoMoreSourcePac kages lets bugs be fixed on a mainline during a release's code freeze, not all bugs that happen to be Fix Committed on release day will have their fixes included in the release, and determining the subset that have been included would be too much work (as prefigured by the current dearth of distrorelease bug targeting you mentioned).
I'm unclear about whether you think there is a *useful* distinction between "Fix Committed" and "Fix Released" at all. If so, how would the distinction help in daily work?