Comment 4 for bug 1483968

I think the right way to implement this is to extend lp-assigner.py so that it checks milestone status, release series, and development focus in launchpad, and adds missing milestones.

For example, now that 7.0 milestone is released, a non-closed bug targeted to 7.0 and not targeted to any MU milestone in any release series would be additionally targeted to 8.0 milestone in 8.0.x series (with status, priority, and assignee copied from 7.0.x), and then marked as Won't Fix for 7.0.x.

If a bug is targeted to 7.0 and is targeted to an MU milestone in any release series, it would be additionally targeted to 8.0 milestone in 8.0.x series (with status, priority, and assignee copied from 7.0.x), and then (reusing the current lp-assigner.py logic) is targeted to the 7.0-updates milestone in 7.0.x release series (Vitaly Sedelnik: please confirm if you prefer it to be 7.0-mu-1 instead).