2009/3/4 Conrad Taylor <[email protected]>

> On Wed, Mar 4, 2009 at 5:59 AM, Colin Law <[email protected]> wrote:
>
>> 2009/3/3 Phlip <[email protected]>
>>
>>>
>>> anrake wrote:
>>> > Hi,  I'm a little bit behind the curve I guess.  I need to upgrade my
>>> > app from Rails 1.2.6 to the most recent version 2.2.2.  Are there any
>>> > complete guides (including Peepcodes or Pragmatic pdf books) that give
>>> > you a comprehensive guide on how to upgrade your application?
>>>
>>> I did it to several programs like this:
>>>
>>>  - edit environment.rb and upgrade the version
>>>  - rake rails:update
>>>  - run all the tests
>>>  - fix one warning or error
>>>  - revert everything in config (leave the new JS)
>>
>>
>> I don't understand what is meant here. Do you mean go back to previous
>> version of Rails?
>> If not then what?
>>
>
> @Colin Law - Philip is saying that you do the upgrade and part of the
> upgrade process is to
>                     change RAILS_GEM_VERSION in your environment.rb to the
> version that you're
>                     upgrading to (i.e. 2.2.2).  Also, you'll have to run
> the 'rake rails:update' to update both
>                     configs, scripts and public/javascripts for your Rails
> application.  Now, you'll be at the
>                     point where you'll simply execute 'rake test' which
> runs all unit, functional and integration
>                     tests.
>

@Conrad - I got that bit, it is the '- revert everything in config (leave
the new JS)' that I do not understand.


>
>>
>>
>>>
>>>  - pass all the tests
>>>  - integrate
>>
>>
>> I don't understand 'integrate' in this context either I am afraid.
>>
>>
>>>
>>>  - repeat until no more warnings or errors
>>>
>>
> Finally, you'll continue to execute 'rake test' until you have fixed all
> the failing
> test(s) within your Rails application.
>
> Good luck,
>
> -Conrad
>
>
>>
>>> The point of unit tests and to TDD is to make the smallest changes
>>> possible, and
>>> relentlessly test each change. But upgrading a major version tick is a
>>> big
>>> change, so you must force the upgrade to work incrementally, as a series
>>> of
>>> small changes.
>>>
>>> If you get stuck, you can always revert and start again.
>>>
>>
>>>
>>> --
>>>    Phlip
>>>
>>>
>>>
>>>
>>
>>
>>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to