Forum: Ruby on Rails rails 1.2 released!

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
997433f165140d58f52b8c0d1d005dc1?d=identicon&s=25 Patrick Aljord (Guest)
on 2007-01-18 14:14
(Received via mailing list)
94d4d7d1b78391266fea8e739c9405c5?d=identicon&s=25 dankelley (Guest)
on 2007-01-18 14:19
(Received via mailing list)
Count me among those who will download 1.2 when it's on the main
webpage :-)
70ca58d0e0e0eabbdb74d177417d09d7?d=identicon&s=25 augustlilleaas@gmail.com (Guest)
on 2007-01-18 14:21
(Received via mailing list)
Mm, I won't install it until I can go "gem update rails" and get 1.2.
Df5e7adb20adae6c120b04e7cafb15a0?d=identicon&s=25 Rob Sanheim (rsanheim)
on 2007-01-18 14:54
(Received via mailing list)
There is a blocker open right now against some of the DB adapters that
break 1.2.  Its a small syntax error, but just be fore-warned: don't
upgrade until its really "official".

- rob
D35d964695abd1bac108370eaf001af3?d=identicon&s=25 Andrew Selder (aselder)
on 2007-01-18 17:26
(Received via mailing list)
I did gem update rails this morning

and surprise, surprise, I got 1.2 :):):)

Andrew
6edd67c92a1dab5eb23fed79f3c18564?d=identicon&s=25 DHH (Guest)
on 2007-01-18 18:01
(Received via mailing list)
> There is a blocker open right now against some of the DB adapters that
> break 1.2.  Its a small syntax error, but just be fore-warned: don't
> upgrade until its really "official".

What rob said. I just pushed the fix to the ActiveRecord gem. Making
the release official now ;)

-- david
0ab6a5abab167b409f58d280dc59a229?d=identicon&s=25 Faisal N Jawdat (Guest)
on 2007-01-18 18:08
(Received via mailing list)
On Jan 18, 2007, at 12:00 PM, DHH wrote:
> What rob said. I just pushed the fix to the ActiveRecord gem.
> Making the release official now ;)

Assuming propagation delays vs. our own impatience, how do we know we
have the fixed version?  ActiveRecord 1.1.5?

-faisal
Bce1d1b7c3ec7b577dcb42e254899e6b?d=identicon&s=25 Michael Schuerig (Guest)
on 2007-01-18 18:27
(Received via mailing list)
On Thursday 18 January 2007 18:07, Faisal N Jawdat wrote:
> On Jan 18, 2007, at 12:00 PM, DHH wrote:
> > What rob said. I just pushed the fix to the ActiveRecord gem.
> > Making the release official now ;)
>
> Assuming propagation delays vs. our own impatience, how do we know we
> have the fixed version?  ActiveRecord 1.1.5?

If you're using one of the affected database adapters your app will
throw an exception at you right from the start. If it seems to work it
does work. Or something to that effect.

Michael

--
Michael Schuerig
mailto:michael@schuerig.de
http://www.schuerig.de/michael/
Ef3aa7f7e577ea8cd620462724ddf73b?d=identicon&s=25 Rob Biedenharn (Guest)
on 2007-01-18 18:35
(Received via mailing list)
On Jan 18, 2007, at 12:00 PM, DHH wrote:

>
>> There is a blocker open right now against some of the DB adapters
>> that
>> break 1.2.  Its a small syntax error, but just be fore-warned: don't
>> upgrade until its really "official".
>
> What rob said. I just pushed the fix to the ActiveRecord gem. Making
> the release official now ;)
>
> -- david

Is there a way to clean up the warning when using a new project
running against the gem?

./script/../config/boot.rb:29:Warning: require_gem is obsolete.  Use
gem instead.

I've been running against a frozen version in vendor/rails for so
long that I was surprised by this warning.  Sure I can do the s/
require_gem/gem/ on that line, but I have to shield my eyes from the
admonition on the first line "# Don't change this file."

Is there a better way?

-Rob

Rob Biedenharn    http://agileconsultingllc.com
Rob@AgileConsultingLLC.com
Skype:  rob.biedenharn
4b380a5c26ad0d43687249015276825a?d=identicon&s=25 Alexis (Guest)
on 2007-01-21 02:55
(Received via mailing list)
Hi, I changed the two lines in boot.rb but I feel kinda bad, are there
any options?
6edd67c92a1dab5eb23fed79f3c18564?d=identicon&s=25 DHH (Guest)
on 2007-01-21 06:13
(Received via mailing list)
> Hi, I changed the two lines in boot.rb but I feel kinda bad, are there
> any options?

Don't feel bad. Perfectly legit. We'll be jumping ship from require_gem
to gem in the next release anyway. Consider yourself ahead of the curve.
This topic is locked and can not be replied to.