Please catch me on the IRC. We can try to solve the problem. I'd be interested what is possibly wrong with the 1.1.0.rc1 and fix it before 1.1.0 goes live.
Pavel On Mar 19, 9:42 pm, Jon Hancock <[email protected]> wrote: > thanks Pavel, I'll have another go at trying to figure out why my > current app isn't working in the 1.1.0.pre gem release but is working > well in the 1.1.0.pre I built in December. I was only asking about > 1.9.2 to think about options for getting out of this mess. > > ~Jon > > On Mar 19, 8:26 am, Pavel Kunc <[email protected]> wrote: > > > > > I'm running as well on 1.9.1 + 1.1.0.rc1. I tired to run my app on > > 1.9.2 and there were no problems I can remember. However 1.9.2 being > > just a preview can have quite a few bugs. I wouldn't run it in > > production. > > > Once 1.9.2 is out (at least rc) we will make sure Merb runs smoothly > > there. > > > BTW by "string model" you mean Encoding stuff? > > > Pavel > > > On Mar 19, 6:47 am, Jon Hancock <[email protected]> wrote: > > > > Anyone using ruby 1.9.2 on merb1.1.0.rc1? > > > I'm using 1.9.1 on merb 1.1.0.pre (built from git in December). > > > I've been having trouble upgrading to the 1.1.0.pre gem release as > > > discussed in a previous thread. > > > > Are their clear benefits to going to 1.9.2? What kind of things would > > > I need to worry about (besides of course checking my dependent gems > > > work)? My app was built with 1.9.1 in mind so I'm using the 1.9 > > > string model heavily. Any change there with 1.9.2? > > > > thanks, Jon -- 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.
