Hey, guys. First off, I''d like to say thanks for all the hard work. Rails 3 is a heck of a piece of software. I''ve got a quick question for the devs here. My company''s trying to build a new product using Rails 3 and we''re encountering a few problems. Specifically, respond_with is failing silently in some important scenarios and config.threadsafe! seems to be broken. We''ve opened up lighthouse tickets with more detail. My question is this: Are responds_with and config.threadsafe! on your development radar right now, or are other things taking priority? Just to be clear, I am NOT asking anybody to drop what they''re doing to work on our problems. I just want to know if our priorities intersect with the work that''s happening to get Rails 3 out the door. Here''s the lighthouse tickets, for reference: "config.threadsafe! appears to be broken" https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/4095 "respond_with fails silently" https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/4088 Thanks in advance! Dave Varvel Technical Lead, Mad Wombat Software -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Jeremy Kemper
2010-Mar-03 16:12 UTC
Re: A question about respond_with and config.threadsafe!
Hi Dave, On Tue, Mar 2, 2010 at 9:46 PM, Dave Varvel <megaduck@gmail.com> wrote:> Hey, guys. First off, I''d like to say thanks for all the hard work. > Rails 3 is a heck of a piece of software. > > I''ve got a quick question for the devs here. My company''s trying to > build a new product using Rails 3 and we''re encountering a few > problems. Specifically, respond_with is failing silently in some > important scenarios and config.threadsafe! seems to be broken. We''ve > opened up lighthouse tickets with more detail. > > My question is this: Are responds_with and config.threadsafe! on your > development radar right now, or are other things taking priority? > > Just to be clear, I am NOT asking anybody to drop what they''re doing > to work on our problems. I just want to know if our priorities > intersect with the work that''s happening to get Rails 3 out the door. > > Here''s the lighthouse tickets, for reference: > > "config.threadsafe! appears to be broken" > https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/4095 > > "respond_with fails silently" > https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/4088 > > Thanks in advance! >These are both blocker bugs. They''ll be fixed before the next beta release. Thanks so much for pounding on the beta. It''s just what the doctor ordered. jeremy -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Dave Varvel
2010-Mar-03 18:02 UTC
Re: A question about respond_with and config.threadsafe!
Hey, no problem. Thanks for building a great framework. -Dave On Mar 3, 8:12 am, Jeremy Kemper <jer...@bitsweat.net> wrote:> Hi Dave, > > > > > > On Tue, Mar 2, 2010 at 9:46 PM, Dave Varvel <megad...@gmail.com> wrote: > > Hey, guys. First off, I''d like to say thanks for all the hard work. > > Rails 3 is a heck of a piece of software. > > > I''ve got a quick question for the devs here. My company''s trying to > > build a new product using Rails 3 and we''re encountering a few > > problems. Specifically, respond_with is failing silently in some > > important scenarios and config.threadsafe! seems to be broken. We''ve > > opened up lighthouse tickets with more detail. > > > My question is this: Are responds_with and config.threadsafe! on your > > development radar right now, or are other things taking priority? > > > Just to be clear, I am NOT asking anybody to drop what they''re doing > > to work on our problems. I just want to know if our priorities > > intersect with the work that''s happening to get Rails 3 out the door. > > > Here''s the lighthouse tickets, for reference: > > > "config.threadsafe! appears to be broken" > >https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/4095 > > > "respond_with fails silently" > >https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/4088 > > > Thanks in advance! > > These are both blocker bugs. They''ll be fixed before the next beta release. > > Thanks so much for pounding on the beta. It''s just what the doctor ordered. > > jeremy-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.