"So, it's out. What do we do?"
How about
1. a version-aware environment.rb in trunk and release versionsimmediately, so
that those who must can upgrade their systems to Rails1.1 and keep Typo running
2. publishing a list of the problematic areas of current app
3. re-focusing on getting all the legacy junk out the application now
I'm assuming the members of the commit team are most familiar with thecode and
they might offer specific suggestions on how to fix it, or atleast what the
biggest problems are. If a list is posted here, perhapsit will attract some
help.
david richardson--www.channel200.net
_______________________________________________
Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list
