Thanks Pavel and Yehuda. I think wiki documentation on how to move a merb app to Rails 3 would be tremendously helpful. There have been numerous blog articles on how Rails 3 differs from Rails 2.x, but I've seen nothing on how it differs from merb 1.1. Whether a transition strategy is single shot or incremental, I think providing whatever guidance is required to make the transition would be in the spirit of the comments made when the merge was originally announced.
Mark. On Apr 27, 5:45 pm, Pavel Kunc <[email protected]> wrote: > I'm willing to help anybody with my knowledge of Merb to contribute > changes needed for Rails3-ish version of Merb. However I don't > personally have any spare time to do the actual coding in this > direction. > > Question would be what is needed to allow the easy transition. In my > opinion if someone wants to migrate to Rails3 from Merb than there > always be cost of the transition. If the transition is done in one go > or incremental IMHO doesn't change the cost of it much. If I'd like to > move I'd do it in one go rather than hanging in between the > frameworks. > > What I can say is coming to Merb is: > - full support ActiveModel API which means you can use ActiveRecord 3 > (merb_activerecord is outdated I think). > - probably ActiveSupport integration (there is still ongoing debate). > The dual extlib/AS3 can be expected. > - there will be changes to Rack integration which brings Merb closer > to Rails 3 > > This two changes will allow you to use some of the Rails 3 features, > for more stuff Jacuqes wanted to do something about this and there is > an idea shaping to provide merb_rails3 gem. The problem I currently > have is my limited knowledge of Rails 3 to be honest. > > There are people doing the guide which helps with Merb -> Rails3 > transition. I'll hopefully find the links/tweets which is yet another > way how to help people with the transition. I'd love to create wiki > page on the github.com/merb with information and resources about the > Merb -> Rails 3 transition. > > Yehuda and Carl are super busy with delivering Rails 3 and Bundler > project and I totally understand that it's near to impossible to work > on the Merb->Rails3 transition. And honestly, I don't feel they > obliged to. > > I think people who're about to switch should drive the contributions. > And as I've mentioned people are working on it. > > I'll support/help/accept contributions if it doesn't cause current > Merb users to suffer. > > Pavel > > On Apr 27, 7:06 pm, Yehuda Katz <[email protected]> wrote: > > > > > Mark, > > > I'd still be interested in that, but the new core team (Pavel, etc.) have > > expressed that they specifically do *not* want to go in that direction. > > > Yehuda Katz > > Developer | Engine Yard > > (ph) 718.877.1325 > > > On Tue, Apr 27, 2010 at 5:02 AM, MarkMT <[email protected]> wrote: > > > It's been a bit quiet here lately - discussion seems a bit bursty, but > > > Pavel et al always seem very responsive to me. My bigger > > > disappointment is that the commitment from the original core team to > > > provide a series of incremental releases of merb that transition it to > > > Rails 3 no longer seems to be on their radar. At the moment, it isn't > > > clear to me what that transition is going to look like. > > > > On Apr 24, 4:28 pm, Pavel Kunc <[email protected]> wrote: > > > > Ming if you need something urgent best is to ping me in #merb. Usually > > > > try to be responsive as possible. Have to say that I've been now 2 > > > > weeks off. > > > > > Pavel > > > > > On Apr 24, 6:57 pm, Ming <[email protected]> wrote: > > > > > > One upside is that the support base should be greater. This is place > > > > > is a ghost town for support. Most merb users seem to be hackers or > > > > > developers. The average joe is SOL here. #merb useful if you're > > > > > lucky or persistent enough to get a sympathetic ear. I knew the > > > > > disparity in userbases going in but needed easy datamapper and > > > > > something else provided by merb. > > > > > > -- > > > > > 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] <merb%[email protected]>. > > > > > For more options, visit this group athttp:// > > > groups.google.com/group/merb?hl=en. > > > > > -- > > > > 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] <merb%[email protected]>. > > > > For more options, visit this group athttp:// > > > groups.google.com/group/merb?hl=en. > > > > -- > > > 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] <merb%[email protected]>. > > > For more options, visit this group at > > >http://groups.google.com/group/merb?hl=en. > > > -- > > 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 > > athttp://groups.google.com/group/merb?hl=en. > > -- > 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 > athttp://groups.google.com/group/merb?hl=en. -- 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.
