similar to: Rails 1.1 is coming--when and what remains to be done?

"Rails 1.1 is coming" - Feb 26, 2006 post in rails-core * http://www.ruby-forum.com/topic/55991 Final Drive Candidates (highlighted for review by core members) * http://dev.rubyonrails.org/report/19 Potential Rails 1.1 Blockers * http://dev.rubyonrails.org/report/10 Did you know you can run many different versions of Rails on the same physical server? This means you can test

The Asterisk development team is pleased to announce new releases of Asterisk, Asterisk-Addons, Zaptel, and for the first time, DAHDI. This is a set of coordinated releases intended to begin the transition from Zaptel to DAHDI; for the reasons why this is being done, please see: http://blogs.digium.com/2008/05/19/zaptel-project-being-renamed-to-dahdi/ The list of packages released today

The Asterisk development team is pleased to announce new releases of Asterisk, Asterisk-Addons, Zaptel, and for the first time, DAHDI. This is a set of coordinated releases intended to begin the transition from Zaptel to DAHDI; for the reasons why this is being done, please see: http://blogs.digium.com/2008/05/19/zaptel-project-being-renamed-to-dahdi/ The list of packages released today

Hi, I just upgraded to rails 1.1 this morning and i am getting a variety of errors from tests that were passing effortlessly on the previous edge release (i froze several weeks ago, so I not sure what version that was). Has anyone else experienced these types errors with the new rails: I have several errors that are grouped around create and destroy commands the errors are similar, first the

The Asterisk Development Team is pleased to announce the the second release candidate of 1.6.0.11, the release of 1.6.1.2, the first release candidate of 1.6.1.3, and the fourth beta of 1.6.2.0. These releases are available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ . The release of 1.6.1.2 fixes a remote crash security vulnerability in the RTP stack. The

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On June 30th, FreeBSD 7.2 will reach its End of Life and will no longer be supported by the FreeBSD Security Team. Users of this release are strongly encouraged to upgrade to FreeBSD 7.3 before that date; FreeBSD 7.3 will be supported until the end of March 2012. Please note that since FreeBSD 7.1 has been designated for

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On June 30th, FreeBSD 7.2 will reach its End of Life and will no longer be supported by the FreeBSD Security Team. Users of this release are strongly encouraged to upgrade to FreeBSD 7.3 before that date; FreeBSD 7.3 will be supported until the end of March 2012. Please note that since FreeBSD 7.1 has been designated for

The Asterisk Development Team is pleased to announce the the second release candidate of 1.6.0.11, the release of 1.6.1.2, the first release candidate of 1.6.1.3, and the fourth beta of 1.6.2.0. These releases are available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/ . The release of 1.6.1.2 fixes a remote crash security vulnerability in the RTP stack. The

A postdoctoral fellow position in computational biology is anticipated to open in the fall of 2009 at University of Washington, Seattle, WA. The candidate will join a multi-disciplinary group working on edge-cutting research problems in computational biology. Job Description We seek a highly motivated and diligent researcher at the early stage of academic career with the ability to carry out

A huge thanks to all the rails developers that worked so hard to improve rails after the 1.0 release! Only 8 tickets remain in the FD report. Next Final Drive (what will be fixed before Rails 1.1) http://dev.rubyonrails.org/report/14 #4234 AR serialization broken with PostgreSQL/Ruby 1.8.2 ActiveRecord David 03/14/06 #4155 type_name_with_module fails, throws Uninitialized Constant

A postdoctoral fellow position in computational biology will be available starting June 1 2009 at University of Washington, Seattle, WA. The candidate will join a multi-disciplinary group working on edge-cutting research problems in computational biology. Job Description We seek a highly motivated and diligent researcher at the early stage of academic career with the ability to carry out

A postdoctoral fellow position in computational biology will be shortly available at University of Washington, Seattle, WA. The candidate will join a multi-disciplinary group working on edge-cutting research problems in computational biology. Job Description We seek a highly motivated and diligent researcher at the early stage of academic career with the ability to carry out research

Hello Ruby group, I hope you can help me out with a search I am doing for a client of mine. They are looking to add a web UI designer to our rapidly growing engineering team. Candidates for this position should have a minimum of 2 years of web UI development experience including Ruby on Rails, Prototype.js and Web Services. The Web Interface Developer will be a member of the front-end development

Firstly, Congrats to the Rails team for the 1.1 release! I installed Rails using the package created by Tony Arnold, referenced here: <http://tonyarnold.com/articles/2005/08/10/rolling-with-ruby-on-rails-on-mac-os-x-tiger-for-beginners> I did the upgrade to Rails 1.1 and all went well. Now, however, I seem to have two sets of gems installed. Doing a ''gems list'', I see:

I''ve been running edge_rails on ruby 1.8.2 for a while pretty successfully. Today, I decided to unfreeze_rails, install the new gem for 1.1 and then while I was at it, upgrade to Ruby 1.8.4. I did the whole configure, make, make test, make install. When I fired up rails, I started getting all sorts of errors:

Currently I''m using the RJS plugin for my app. After I upgrade to the soon-to-be-released 1.1 (which has RJS support built in), will anything break after removing the plugin? Has anyone messed with the release candidate and RJS yet? -- Posted via http://www.ruby-forum.com/.

Just upgrade from rails 1.0 to 1.1 Everytime I run the unit and/or functional tests, I got the following messages. Is there something I need to do to remove? I am not sure where to start. Thanks in advance. /usr/lib/ruby/gems/1.8/gems/activerecord-1.14.2/lib/active_record/validations.rb:334: warning: `*'' interpreted as argument prefix

I''ve noticed that after upgrading rails to 1.1, the ''freeze_gems'' task fails due to an error. I have no idea how to submit a fix, but wanted to post it here in case anyone else is having this issue. You''ll have to navigate to the folder that is appropriate for your setup: Go to "/usr/local/lib/ruby/gems/1.8/gems/rails-1.1.0/lib/tasks" Open up

i just upgraded to rails 1.1 yesterday and since then i could?nt make it work with mysql, for example i have my database "todo" and one table "todos", i create the app and generate the model but when i try to generate the scaffold with "ruby script/generate scaffold Todo Todo" i get this error " error Before updating scaffolding from new DB schema, try

Hello all, I''m kinda going through a rocky upgrade to rails 1.1 and I can''t find much on google about this. When I run my tests I get this: $ rake (in /home/www/art2) /usr/bin/ruby -Ilib:test "/usr/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake/rake_test_loader.rb" "test/functional/panoramas_controller_test.rb"