Hi Hans -
I have recently completed an upgrade of 3 applications (with 2 more to
go) with more than a dozen plugins from Rails 2.3.5 to Rails 3.0.6.
My process was to do not only upgrade each app but to convert each
plugin into a rails engine-gem.
I made a Rails3 branch of each of our repo's.
Colin
I thought that the conguration filés and environment filés were
different
But that may not be the case or New filés may be generated
In addition the controls templates for rails 3 and later rails 2
version use
respons to and I do not use that but that is another problem and
respons to may
On 5 May 2011 11:22, Hans hans.marmo...@klockholm.se wrote:
Colin
I thought that the conguration filés and environment filés were
different
But that may not be the case or New filés may be generated
Have a look at
http://railscasts.com/episodes/225-upgrading-to-rails-3-part-1
it should help
That's great. I also prepare my app for migration from 2.3.9 to 3
I started to cover all controllers with Rspec(and do a little
refactoring). Then I'll cover all models. And only then I'll generate
new Rails 3 app, copy my specs, and start to copy the code from old
app to make specs pass. That's
... and i 100.times sorry again I wasn't writing specs before the code
at first place
On Thu, May 5, 2011 at 3:16 PM, Vladimir Rybas vladimirry...@gmail.com wrote:
That's great. I also prepare my app for migration from 2.3.9 to 3
I started to cover all controllers with Rspec(and do a little
Exequiel.
That was also my approach but Colin seems to prefer the other
approach.
Maybe its a question about control. I think your approach gives more
control to the uppgrading process than Colins
If anything goes wrong using Colins approach then it could be the old
code but also the combination
On 3 May 2011 08:58, Hans hans.marmo...@klockholm.se wrote:
In addition my controller does not follow the proposed structure that
is generated in a rails 3 scaffold with respond_to do |format|, which
will be corrected with Exequiel's approach
I do not understand what you are saying here.
Actually I didn't have many problems with Rails (if a remember well),
just with some methods, like link_to, response_to, etc and many
warnings, they were catched doing tests. The files into config
directory are very different between RoR v1.2.3 and v3.0.0, it was
using fastcgi and the pagination
Thanks for your advise
I will follow them
However, I am thinking of limiting myself mostly to functional test
(testing controllers).
Is that ok ?
Your suggestions with source control an testdriven development implies
that I should make a new rails 3 application copying source from my
old
On 2 May 2011 14:30, Hans hans.marmo...@klockholm.se wrote:
Thanks for your advise
I will follow them
However, I am thinking of limiting myself mostly to functional test
(testing controllers).
Is that ok ?
You should certainly have unit tests for any logic in the models.
Your suggestions
I upgraded an app from rails 1.2.3 to rails 3. First, I installed RVM
with both Rails versions (gemset: rails1.2.3 and rails3.0.0), I
created a new Rails 3 app from scratch and I was adding the
controllers (helpers, views, etc) one by one. It was a lot of work but
I was sure that all things were
11 matches
Mail list logo
