For our project source code we use standard SVN structure: trunk, branches, tags. Most of development efforts is happening in trunk.
I wonder, what’s the best way to organize project’s Liquibase changeSets in SVN considering above structure?
I want to avoid bulking up change sets for previous releases in the same place, but at the same time I don’t want to delete old files from trunk. So current structure goes to something like
which kills a bit an idea of trunk/ for LQ changeSets but also keeps them saved for later.
Any suggestions how to do it better?