Migrations + Teams + possible SVN Conflicts

Hi Guys,

I've got a team of people working on a Rails Project. They work
independently on various different modules. Each sub team/developer
creates relevant migrations for the component they work on and then
check-in. There are no conflicts as well since they all add new
migration files. However we end up with multiple migrations with the
same migration number. What is the ways other Rails team avoid this

There was a plugin just released to help with this (by renumbering them) but I can't for the life of me remember the name.