Yup, Rails had a similar problem back in 1.0 days where it had a sequential migration number. Then it moved to essentially date formatted migration names in 2.

Yup, Rails had a similar problem back in 1.0 days where it had a sequential migration number. Then it moved to essentially date formatted migration names in 2.0 and that solved that. Your manifest idea seems interesting, have to remember that one...