A new topic, 'changeSets management in SVN and releases', has been made on a
board you are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=694.new#new
The text of the topic is shown below:
Hello
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
trunk/Liquibase/release-1.9
trunk/Liquibase/release-1.8
etc.
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?
Thanks,
Maciek
Unsubscribe to new topics from this board by clicking here:
http://liquibase.org/forum/index.php?action=notifyboard;board=1.0
Regards,
The Liquibase Community Forum Team.
------------------------------------------------------------------------------
Automate Storage Tiering Simply
Optimize IT performance and efficiency through flexible, powerful,
automated storage tiering capabilities. View this brief to learn how
you can reduce costs and improve performance.
http://p.sf.net/sfu/dell-sfdev2dev
_______________________________________________
Liquibase-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/liquibase-user
