Rails 3.0: Beta 4 now, RC in days
Posted by David June 08, 2010 @ 10:20 PM
RailsConf 2010 is underway and what better occasion to do the final stage of the Rails 3 beta program. We’re very pleased to announce Rails 3 beta 4, which we’ll be hammering on and tuning during RailsConf.
At the end of RailsConf, we’ll be putting out the release candidate. So if you’re at the conference, and even if you’re not, now is the time to give upgrading a chance or even starting a new app. We’re all responsible for making this release solid, please join the fun.
You can install the latest beta with gem install rails --pre
Since we’re so close to release now, it’s also a great pleasure to introduce the new Rails 3 screencast series by Gregg Pollack and EnvyLabs. They’ve done an awesome job putting together six episodes and more are coming. You can also read along in their great Rails 3 slides from the RailsConf tutorial.
I also gave a keynote on Rails 3 this morning at RailsConf, so you can enjoy the slides.
Let’s race to the finish line together.
Well done guys, I’ve been following progress on Github all day. Are there any steps that are required to upgrade an existing Rails 3 app other than flipping the gem over?
great job guys! we’ve already moved three apps to rails3 beta3 and they’re working fine. looking forward to upgrading to beta4.
hope rspec, remarkable and others will keep up with the pace.
This is fantastic! I love the great selection of screencasts. So helpful! Keep it up. Can’t wait for the rails 3 ecosystem to build up and dominate.
Perfect!
Congrats! Been looking forward to these gems being released for a while now—can’t wait for the final 3.0.0 release!
Sweet, Just in time :)
Stoked. Love rails 3, it seems easier than rails 2.
Need gem memcache for Beta 4, but it fails to install in CentOS 5
that’s if you use memcached…
my i18n call to a string using t helper, now didnt recognize html entities, is not html_safe the t() helper?
Awesome! Nice work!
Raphael Costa, to make t() helper return safe you need the keys to be =~ /(\b|_|\.)html$/ so please check that otherwise please open an issue on LH.
Rails 3 looks delicious :) Totally awesome job, guys!
Thanks Santiago. I saw this in the github commit… to be html_sage the i18n field named needs end with _html or .html … maybe a release notes of beta4 will help evertybody
Hope this isn’t a disaster like 2.3.x was :(
This rails_xss crap is really terrible – I don’t want to use it and in the fact I’m not using it (it slows down app dramatically), so the only thing I had to do was adding in one helper html_safe method. Normally for xss protection I’m using xss_terminate plugin for escaping user input – that’s all.
I’m asking – why the heck Rails team tries to force me to use some plugin? I’m aware of xss attacks and I know exactly what to do.
Have been using rails 3 for a while now and it really is full of sweet, sweet stuff :o)
Looking forward to RC and final.
enviroment: macOsx snow leopard ruby 1.9.1
sudo gem install rails—pre (21 gems installed) . . . rails test_app
(nothing happens)
instead rails usage message appears
George its been replaced with..
rails new app_name
Give us some release notes!
@zZzZ:
Why not use one of the other Ruby web frameworks/libraries?
That way you can assemble whatever pieces you need in any way you like, without being restricted by someone else’s choices.
File not found: lib <<<<< WTF?!!!!!!!!
@j:
But AFAIR it was main goal for ror3 – not forcing users to use this or that, isn’t it?
On windows xp, ruby 1.9.1, the gems installed fine, but when the ri docs were being installed I got:
11 gems installed Installing ri documentation for activesupport-3.0.0.beta4… Installing ri documentation for activemodel-3.0.0.beta4… Installing ri documentation for actionpack-3.0.0.beta4… Installing ri documentation for arel-0.4.0… Installing ri documentation for activerecord-3.0.0.beta4… ERROR: While executing gem … (Errno::EINVAL) Invalid argument – ./</cdesc-><.yaml
I’m having the same problem as Mark Richman. Any hint on how to solve it?
Hm. More problems. I had successfully (or so I thought) installed the beta 4 – all the gems installed fine (again, on Windows XP), but it’s still using the old beta3 rails command:
from ‘gem list’: rails (3.0.0.beta4, 3.0.0.beta3)
from ‘rails -v’: C:\>rails -v Rails 3.0.0.beta3
@John T:
Try to manually remove old rails and railties gems and then install rails beta4 again. This should help.
Uninstalled beta 3, installed beta 4 – no problems! Thanks guys!!
My first attempt at fixing was doing:
gem uninstall rails
gem just wanted to uninstall just the rails gem (both beta 3 and beta 4). I let it remove both, then redid the gem install rails—pre. That just reinstalled the rails gem, but I was still getting beta 3 for rails -v. So I did a gem cleanup, and that, magically, fixed it. ‘rails -v’ now returns beta4.
Please, Release Notes!!!. Rails 3 Beta 4 Changed a lot of thing and we need to search in the Github commits what changed after the surprise or error.
Beta 4 changed too lot, I have to modify my code according github commits
Is there a video of the keynote?
congrats!
Already ported a huge app under rails 3 head.
For the ones that are plan to port their apps, moving to rails 3 could take you some times and you should keep some gems under the right branch (ie. factory-girl, authlogic) but it will works at the end, and will works very well.
Just keep in mind that this is a work in progress release (Beta at the end). Follow GitHub commits is probably the best things to do for now to keep aligned with the changes. Keep your ported app in staging until a final release will be out.
Great job guys!
Is Beta 4 compatible with the stable releases of Ruby?
Release notes: “Note that Ruby 1.8.7 p248 and p249 has marshaling bugs that crash Rails 3.0.0. Ruby Enterprise Edition have these fixed since release 1.8.7-2010.02 though. On the 1.9 front, Ruby 1.9.1 is not usable because it outright segfaults on Rails 3.0.0…”
Here’s a wierd one. Updating to beta 4 on OS X (10.6.3), I got:
john$ sudo gem install rails—pre Password: Successfully installed bundler-0.9.26 Successfully installed rails-3.0.0.beta4 2 gems installed Installing ri documentation for bundler-0.9.26… Installing ri documentation for rails-3.0.0.beta4… File not found: lib
but doing a gem list shows all of the rails gems were installed:
actionmailer (3.0.0.beta4, 3.0.0.beta3, 2.3.5, 2.2.2, 1.3.6) actionpack (3.0.0.beta4, 3.0.0.beta3, 2.3.5, 2.2.2, 1.13.6) actionwebservice (1.2.6) activemodel (3.0.0.beta4, 3.0.0.beta3) activerecord (3.0.0.beta4, 3.0.0.beta3, 2.3.5, 2.2.2, 1.15.6) activeresource (3.0.0.beta4, 3.0.0.beta3, 2.3.5, 2.2.2) activesupport (3.0.0.beta4, 3.0.0.beta3, 2.3.5, 2.2.2, 1.4.4)
?
“documentation for activerecord-3.0.0.beta4… ERROR: While executing gem … (Errno::EINVAL) Invalid argument – ./</cdesc-><.yaml”
Got this during installation on Windows 7×64 with Ruby 1.9.1 p378 installed with the RubyInstaller Final.
I am encounter the wierd case also: Successfully installed rails-3.0.0.beta4 1 gem installed Installing ri documentation for rails-3.0.0.beta4… File not found: lib
RubyGems Environment: – RUBYGEMS VERSION: 1.3.7 – RUBY VERSION: 1.9.1 (2010-01-10 patchlevel 378) [x86_64-linux] – INSTALLATION DIRECTORY: /home/bugu/.rvm/gems/ruby-1.9.1-p378 – RUBY EXECUTABLE: /home/bugu/.rvm/rubies/ruby-1.9.1-p378/bin/ruby – EXECUTABLE DIRECTORY: /home/bugu/.rvm/gems/ruby-1.9.1-p378/bin – RUBYGEMS PLATFORMS: – ruby – x86_64-linux – GEM PATHS: – /home/bugu/.rvm/gems/ruby-1.9.1-p378 – /home/bugu/.rvm/gems/ruby-1.9.1-p378@global – GEM CONFIGURATION: – :update_sources => true – :verbose => true – :benchmark => false – :backtrace => false – :bulk_threshold => 1000
I use the script on http://railscasts.com/episodes/190-screen-scraping-with-nokogiri to try it on rails 3 beta4.But it fail on rake task mode and pass on “ruby test.rb” mode. Same rake task pass on Rails 2.3.5. Error msg : no such file to load—nokogiri Ruby version is 1.8.7.OS is ubuntu 9.04.
Any help to solve it ?
Yeahh Rails 3.0 RC comming soon!!!!
People having the File not Found: lib issue. If you run rails -v you’ll see that you still have a workable rails install.
That´s fantastic, can´t wait for the official release – feels good to build on a architecturally improved plattform!
@mark + @francesco:
I had the same problem but I realize that if rails documentation is not installed it is not a problem.
In more detail:
gem install rails—pre it will install the documentation for all the gems (activerecord, actionpack and so on…) but “rails gem” has no documentation so if it fails to install it is not a problem…
I’ve just started using rails (I’ve been a .net mvc junkie for awhile) for a new app I am building. Would you guys recommend using rails 3 b4 or sticking with 2?
I’m assuming that a lot of gems will not have upgraded yet, correct?
@rubiii
http://ruby-lambda.blogspot.com/2010/06/remarkable-400alpha4.html
I didn’t even know about the beta4 release until today.
@chance I am also a asp.net mvc junkie and I would recommend using the 3.0 stuff. It’s very good stuff especially the new active record querying though it’s not linq you’ll feel at home with it.
Looks like there is a minor issue when upgrading to Rails 3 beta 4.
running rails -v leads to “Rails 3.0.0.beta3” while beta 4 is installed.
I guess some file failed to be updated properly ;-)
it says Rails 3.0.0.beta4 for me. Make sure you did Gem install rails—pre, followed by Gem Clean
Just watched the ActiveModel screencast. Attributes is pronounced a-truh-byoots not uh-trib-yoots. Attributes is a noun.
Why does the screen cast not use the new validators?
validates_presence_of should be validates :field, :presence => true
Side Note: Changing the link description for the topmenu from “Code” to “Bugs/Patches” was forgotten for the blog application.
How you coming on that RC you’re working on, eh? Got a big stack of tickets there? Got a nice little release you’re working on there, you’ve been working on for a week? Working on that quite some time, eh?
Stewie FTW.
realised that using ruby-1.9.1-p378 seems to cause trouble when you create a new app, then a new scaffold and try to open that scaffolds index-page… quite some ugly error message crashing webrick. I failed to interpret the error-message in order to find the problem.
Anyway ruby-1.8.7-p249 and ruby-1.9.2-preview3 and ruby-head do not seem to cause the problem. Everything works well. Nice Job, can’t await the RC.
Really excited about Rails 3… Finally!
Uninstalled beta 3, installed beta 4 – no problems! Oyunlar Thanks guys!!
Beta 4 changed too lot, I have to modify my code Oyunlar according github commits
20 months – it’s time to finish….no more extras…..thanks for the hard work….but it’s past time to finish….
take as much time as you need as it´s much more important to do it right, solid and future proof! thank you all for your hard work!
@theworldwaits – calm down. The next time I go to a restaurant and get a free meal make sure you complain about the waiter taking too long.
@dhh – take an extra month just to piss off @theworldwaits
@nate you think this is free? Who do you suppose will make the most money hosting rails? Who do you supplose will be selling the books. Do you suppose that no user invests their time and money in rails? So you suppose that customers are willing to sink money into designs and redesigns based on continuing to push the time back when any of this will be useful? Do you suppose that days should really mean weeks, weeks really should mean months?
1.8.6, 1.8.7, 1.9.1 1.9.2, rvm, 2.3.x, beta,beta,beta….enough already. And the rails folks say that python and django folks ought to look to standardize things? Really?
And I don’t usually go to a restaurant to have a free meal. And maybe that is what is wrong here. Maybe folks think that because this is “free” that it doesn’t matter when it is done. That would be true if there had not been 20 months of blog posts and articles all over the Internet explaining how great and fast and modular and etc. and it’s just a few months away and days away etc., etc.
It’s about managing expectations. If you tell the world to buy into what you are doing because of how great this will be, and give the world a timeline, then leave the world hanging as to what is happening….well, the world will be waiting.
20 months and it’s time to finish. It’s also past time to let the world in on what the delays are, based on the expectations that the rails team gave the world.
The World Waits
It’s all free. They can take however the fuck long they want. Be grateful.
@theworldwaits. How about you chip in with some tickets to speed the process up?
Rails committers owe you nothing. Quite the opposite in fact.
...After all that rubbish, just wanted to say… A HUGE THANKS for all your hard work to the Rails team! WordPress 3 was just released, and the Rails RC is most certainly on it’s way… It’s like Christmas in (nearly) July! :)
It’s all too easy to counter someone like theworldwaits’s comments with a comment about how it’s free, the RoR team owes you nothing, you owe them, etc… While some of that is true, it’s this kind of attitude that will prevent rails from ever being a serious player in the enterprise world,or at least gain enterprise level respect.
@Confused: The kids are all too busy worshiping Heinie to realize that.
Should I start to learn Rails 3 or 2 or Ruby?
Trying out Rails 3? Broken gems?
sudo gem install chuck-norris
On a second thought, you don’t have to sudo it. Chuck will take care of it for you. He was missing in action 25 times.
Ruby then Rails 2 then Rails 3
if you have’t started, of course learn the latest. rails 3 is so good
i’d say learn rails 3. It’s pretty much good to go. There’s stuff to iron out but you won’t notice too much of a change between what’s out now and what’s going to be the final release. Good work rails team, i’m loving rails3
In days means within less than a week… However free it is, making people believes something is coming soon is not a great communication style. So lesson learned for @DHH: Don’t communicate too early so that all those impatient keeps whining somewhere else ;)
In days means within less than a week… However free it is, making people believes something is coming soon is not a great communication style. So lesson learned for @DHH: Don’t communicate too early so that all those impatient keeps whining somewhere else ;)
@theworldwaits – though I agree the alphabet soup of versions is annoying – who really cares. You’re not the product manager paying for rails/ruby development.
Whenever people say how long software takes they are usually wrong. If you develop software you would know this 100% and take all estimates with a grain of salt.
They planned to have a beta release out by last railsconf but that target was a year wrong. As a consolation, the new version of the framework is ridiculously good and includes a lot of features they hadn’t dreamt of implementing.
Beta4 runs great and many people have code in production. The lack of an official release should not prevent you from enjoying the goodness that is Rails3. What they are doing is making sure that the release pushed out has as few bugs as possible. This is the smart/professional thing to do, and great for overall acceptance even if they lose you as a fan.
And Rails2/Merb1 are still nice too, so it’s not like you don’t have frameworks to play with already.
Another grateful developer here. My thanks to the whole Rails team! I’m looking forward to the RC whenever you feel it’s ready!
Are there any start-with-rails3-guides out already? Several books are now delayed.
I’ve been using beta4, and have not yet encountered any show stopper bug yet.
@Confused – It’s not as if “the serious players in the enterprise world” are never delayed. The JBoss AS 5 release is a good example.
@theworldwaits – I can’t see how anybody was ‘left hanging’. Rails is open source. You can check out the code from GitHub. You can browse the issues that are being worked on on LightHouse. The core team frequently blogs on what is going on with the project. I’d say there is a high degree of openness as to what is happening.
I tried to go the lighthouse ticket manager and see if there were any unclaimed tickets that I could pick up to help things along.
It actually seems like everything is under control and there are no unassigned tickets left. Actually, everone who currently holds tickets holds only 1 or 2 of them.
I think the RC is coming pretty soon.
“gem just wanted to uninstall just the rails gem (both beta 3 and beta 4). I let it remove both, then redid the gem install rails—pre. That just reinstalled the rails gem, but I was still getting beta 3 for rails -v. So I did a gem cleanup, and that, magically, fixed it. ‘rails -v’ now returns beta4.”
okay, what do you mean by “I did a gem cleanup”. Because I am having the same problem as you.
PS. I am also using Ruby Version Manager.
ah okay:
$ gem cleanup
^ that fixed it.
great job.. I was having difficulties with beta 3 but now it seems to rock! http://www.hellora.com is shining thanks to you guys.. lets see the big final!
ERROR Encoding::UndefinedConversionError: ”\xC3” from ASCII-8BIT to UTF-8 – # Yehuda Katz (wycats) Yehuda Katz (wycats) June 11th, 2010 @ 12:23 AM
Yep. I have a solution for this. I’ll get it in tomorrow! No surprise…...
@wycats, you’re a freaking hero. Thanks!
in about 11 days, this post will become 1 month old…which will then invalidate its title for RC coming in days…release it already please!
The delay isn’t what’s unprofessional. The buildup of expectation followed by total silence is.
It looks like the RC is just hanging on two more tickets:
https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/milestones/current
One which hasn’t seen any movement in a couple of weeks. The other which #82 made a joke about.
one remaining. but he’ve been to that point already, any new userreport might report a bug to RC. actually this is a really good thing, we don’t want bugs or security issues at release day, do we? everybody is asked to try out beta 4 as this already offers nearly all option the future RC will give you.
The World is now relieved and hopeful again.
It would be nice to hear an update on the situation… I don’t mind if the update is something along the lines of “looks like it will be another month”, but some news would be much appreciated after dropping a bomb like this…
rails 3 RC is now removed from lighthouse app and there was only 1 ticket remaining yesterday. just a guess, but I’m expecting the first RC in the next week.
gem install rails—pre—tty—please
installing on windows.gives the error ‘requires ruby 1.8.7’ I installed both 1.8.7 and 1.9.1
RailsGuides says: “Note that Ruby 1.8.7 p248 and p249 have marshaling bugs that crash Rails 3.0. ... Ruby 1.9.1 is not usable because it outright segfaults on Rails 3.0, so if you want to use Rails 3 with 1.9.x jump on 1.9.2 for smooth sailing.”
But there are no windows installers for either option.
@ed
Try pik: http://github.com/vertiginous/pik
I haven’t used it since I don’t do my Rails development on windows, but it might help if its anything like RVM for linux and mac.
I used the ruby installer to put 1.9.1-p378 on winxp, and gem install rails—pre went fine.
I haven’t done as much on windows as I’ve done on my mac, but basic rails apps are working fine.
As Nick mentioned, pik is under active development: http://github.com/vertiginous/pik/commits/master/
Days hey? how many?
Railsconf is still going on? I didn’t realize it lasted that long. You guys must be tired.
“Your Estimates Suck”—Rework
Agree… For being agile, I don’t get were the deadline on this has blown out by multiples so high.
@J/J2
People are already running Rails3 in production. What are YOU doing (besides complaining)?
what deadline?
On June 8, David said 2 more days—it’s been 20 days or so, and it’s a fair question. Meaning David’s estimate of a unit of two days is now a multiple of 11x over the 2 day baseline. I’d really like to understand what happen and how I can help it not happen again. A lot of people though R3 would have been out over a year ago, or at least I did… just looking to understand the process of release estimates, and have been unable to find anything on this online. It’s a far question, and find it odd that already two people appear to take issue with it.
Rails is a gift and I am happy with 2.3.5 in production. The community of committers may have an opinion as to a schedule. They are the creators.
The critique from spectators is just noise that we should filter in the new order of open source.
This reminds me of @_why’s tweet: ‘when you don’t create things, you become defined by your tastes rather than ability. your tastes only narrow & exclude people. so create.’
If you are not creating, try to avoid annoying those who are.
garyf You must be the most brilliant person in the whole world. Let us bask in your glory. How dare anyone ask why an open-source project is going through a total information embargo.
You are right and you are brilliant. Book authors and publishers needing some idea of when this will stabilize because they have money and time on the line. Screw them!! A twitter tweet from anyone saying, “we’re working on such and such and it will be at least a few days if not a couple of weeks – no – screw you if you have the least bit of interest in when this will stabilize.
You call this open source? When you can’t get any info? Doesn’t the spirit of open source and community require that you give out just at least the tiniest bit of info?
Yes – it sounds as though that you garyf, and only you have ever created anything. And only your opinion, and the opinion of dhh, wycats and a few other matters. And if any of the rest of us have an opinion, it is only background noise compared to your brilliance. Let me bask in it all.
You see, if you are not on the rails team, you are just a “user”, and in the most derogatory and debasing way. And participating in the community in any other way that contributing code directly to rails 3 means you are an insignificant peon.
This is a blog post entitled “beta 4 now, rc in days”. All that people are asking for is the common courtesy to explain what the issue is and how it will work itself out. You see, garyf, in your brilliant creations you might not have heard about blogs. Let me clue you in. They are built to keep people informed. Just a minute or two a day and you can let all of the “little people” (dhh) in on some of the things that are going on.
At this point it has to be asked…why is there total complete lack of any information? Is it out of spite? Control? What is it? This is bizarre and preposterous.
@theworldwaits- As far as information goes-
Nothing is stopping you from keeping tabs on the project development on github. http://github.com/rails/rails shows all the progress going on and hourly commits.
Nothing is stopping you from checking out the tickets on lighthouse. There are 50 remaining tickets on the lighthouse account for the full (non-rc) release ( https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/milestones/27004-rails-3 ).
Nothing is stopping you from installing rails from the current github commits, which will be the rc in all but version (since pretty much all rc tickets are closed).
Nothing is stopping you from reporting any showstoppers you encounter with the most recent versions of rails 3, so they can correct the bugs you find.
Nothing is stopping you from reading all the Rails 3 documentation while you (and the world) waits, so you can hit the ground running once the rc is stamped.
So I’m not sure what the problem is here. Did you base your whole company’s strategy on a specific release date? Did you encounter a problem with edge rails, submit a ticket, and find it ignored? Did you put a specific bet on the the time 3.0 dropped officially?
@theworldwaits
<gratuitous guidance> 1. grab a bag of popcorn 2. sit on the edge of your seat 3. do not hold your breath for too long </gratuitous>The problem is that this is open source and this is a community. Is it a state secret as to what is going on?
Funny how every kid with a computer has an opinion that you should just wait, and be happy with no information unless you are willing to roll up your sleeves and finish a couple of tickets.
Have we forgotten that rails is heavily dependent on plugins and javascript libraries that are themselves open source. Thats right. Rails is just a cheap ruby mvc without jquery or prototype, and all of the useful plugins.
Whats that? You say many of the most useful things in the rails ecosystem weren’t even built by the rails core team? Shocking I know. Yet almost all plugin and gem developers will at least give you a blog post or an email about developments. Usually one guy that has developed a plugin with no resources will keep you more informed than this team, whose sponsored pay comes from those of us who subscribe to services and hosting and buy books from those involved.
It’s just a damn blog post. Is that so hard? Just let us know what is going on. Thats all.
And @nate if I did bet my whole company on a release date, why do you suppose I would have done that after 20 months of blah blah blah, its great, its almost done, just a couple months more….yada yada…we’re brilliant…on and on and on.
Do you think that app design clients aren’t interested in why rails 3 is taking so long?
And now that rails 3 has the interest of many people, and is on the radar of many potential paying clients, we can’t even get a blog post about what is going on?
@theworldwaits
The difference between a customer and a user is that a customer pays for something. Customers should express their expectations. Witness the iPhone4 antenna issues.
Users should be grateful that they have access in the first place.
Lift a finger and try, for once, to be resourceful. As @Nate has already pointed out, an ocean of info is just a few clicks away.
If you must be spoon fed, go buy something else.
I said to go do sudo gem install chuck-norris long ago, but nobody listened. Chuck would take care of it in a blink of an eye.
Yeah, guess all those customers (oh, I mean users) at twitter should just piss off; because they don’t matter. WOW, makes so much sense. Users NOT coders, communities, customers, companies are the center of the world. Without users there is NOTHING.
Yeah, ROR is amazing, but doesn’t mean that someone doesn’t have there head in the clouds either. All and all it doesn’t matter to me if R3 ever comes out. What am interested in is how two days turns into twenty and counting…
J2 – have you thought about emailing DHH personally to let him know how you feel? It’s possible that he doesn’t read the comments here
@J2
I don’t know if you are already involved, but I would like to recommend you to fork this project on github and start to give your contribute http://github.com/rails/rails
in meanwhile get some geen tea and calm down,
yours, libo