I've updated the upstream status of the bugs to "Fix released".
The one you report (bug 605079) was indeed erroneously still not marked as "Fix committed" and so it got automatically shifted to milestone 1.5.5 by a script that we run at the end of the milestone. I didn't find any other bug with the wrong milestone though, note that we push a new SRU only every two releases, so in this SRU there bugs targeted to both 1.5.3 and 1.5.4, hope it's fine.
As mentioned on IRC, I didn't create tasks for all the bugs because at some point someone told me that it was fine to do that for the main SRU bug only, for reducing the overhead. If you prefer to have individual tasks for all the bugs linked to the main SRU request bug, please let me know and I'll do that next time.
I've updated the upstream status of the bugs to "Fix released".
The one you report (bug 605079) was indeed erroneously still not marked as "Fix committed" and so it got automatically shifted to milestone 1.5.5 by a script that we run at the end of the milestone. I didn't find any other bug with the wrong milestone though, note that we push a new SRU only every two releases, so in this SRU there bugs targeted to both 1.5.3 and 1.5.4, hope it's fine.
As mentioned on IRC, I didn't create tasks for all the bugs because at some point someone told me that it was fine to do that for the main SRU bug only, for reducing the overhead. If you prefer to have individual tasks for all the bugs linked to the main SRU request bug, please let me know and I'll do that next time.
Thanks!