Some of us are having problems running vendored edge Rails. See https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2567-unable-to-generate-working-edge-app#ticket-2567-10 The problem seems to have been introduced in a commit on the 23 April, 5 days ago! Why did it take so long to find out that edge Rails ain''t loading? Comments please? John Small
> Some of us are having problems running vendored edge Rails. See > https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2567-unable-to-generate-working-edge-app#ticket-2567-10 > > The problem seems to have been introduced in a commit on the 23 April, > 5 days ago! Why did it take so long to find out that edge Rails ain''t > loading? > > Comments please?Edge rails is likely to be a rough ride for a while until the refactoring for 3.0 slows down. You should probably track 2-3-stable instead. That''s what I''m doing. I''m sure jeremy will get to the ticket when he wakes up. -- Cheers Koz
On Tue, Apr 28, 2009 at 2:51 AM, Michael Koziarski <michael@koziarski.com> wrote:>> Some of us are having problems running vendored edge Rails. > > Edge rails is likely to be a rough ride for a while until the > refactoring for 3.0 slows down. You should probably track 2-3-stable > instead.The CI build for edge is green: http://ci.rubyonrails.org/ If you are having problems, please submit a patch with a failing test that illustrates the problem. Also, I just added the 2-3-stable branch to CI (which is green, yay!) -- Chad