Nice! :) It's a bit of a tip of the hat to merb, really... that it's taking a while to bring Rails up to the integration point...
Wickkkkked :) Julian. On 29/06/2009, at 12:49 PM, Yehuda Katz wrote: > Again, there'll be more tonight, but we are ABSOLUTELY still > planning on an easy transition path. Since we announced the merge, > we've been working hard on cleaning up the internals of Rails so > that such an upgrade path would be possible. As I said at the time, > a transition from one API to another is relatively trivial, but a > transition from a known API to the wilderness is not. Several times, > we've looked at starting to write some transitional APIs for Merb, > but realized we weren't far enough along in the Rails work to > justify doing so without really dicking around the Merb users. I > think we're finally far enough along to justify taking another stab > at some transitional work, though. More details later tonight :) > > -- Yehuda > > On Sun, Jun 28, 2009 at 7:21 PM, Patrick Aljord <[email protected]> > wrote: > The thing I'm more concerned is the 1.1 release we were promised and > even more important, the "easy" upgrade path to rails 3 we were > promised by releasing several versions of merb that would deprecate > poco a poco the old api to make it more simple to upgrade to rails3. > At least that's what I remember from the blog posts announcing the > rails+merb merge but I might be wrong. > > > > > > > -- > Yehuda Katz > Developer | Engine Yard > (ph) 718.877.1325 > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
