Ramaze is still evolving pretty quickly, so the changes between
releases tend to be significant. Sometimes this means that newer
versions of Ramaze will require changes in existing Ramaze apps.
If you're worried about this, I recommend either including a specific
version of Ramaze in a /vendor directory as part of your app or
requiring a specific version using RubyGems. That way you can build
your app against that version of Ramaze and be assured that your app
will run regardless of changes in future releases.
- Ryan
Good suggestion, but one downside is that bug fixes may not back-port well.
Sticking to an older version when an API is changing rapidly also makes
it harder to get help.
I don't want to scare anyone away from Ramaze, but I also don't want
anyone ending up spooked because a project didn't go as smoothly as
expected.
--
James Britt
http://www.rubyaz.org - Hacking in the Desert
http://www.jamesbritt.com - Playing with Better Toys