If you have an SVN branch on which a huge of amount of work has been done, effectively being the main place for development, is there any special way to decide this branch should become the trunk? A project I'm involved with has this situation, it's kind of like taking a branch of your operating-system code and then replacing the entire kernel.
Is there a 'right' or 'wrong' way to handle this? It seems forcing a branch to merge when it's very different doesn't achieve much, if all the trunk changes have been merged to your branch.