Hello, list.
I am doing evaluations of (web) app frameworks at work.
I played around with trails and found it very interesting. But one
certain point at issue is not answered in the docs.
How does Trails cope with the natural evolution process every software
goes through (e.g. an enum is refactored into an own class)?
Is there a recommended strategy for coping with that?
Of course, when there is no data yet (before the first release), it's
trivial. Just wipe out the database and start from scratch. But what
if there is data to be migrated?
Kind regards,
Daniel
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
