-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rails Upgrade #158
Comments
Gayle, Kenny Drobnack On Saturday, February 18, 2012 at 11:36 AM, Gayle wrote:
|
Maybe, I'm not sure. it seems like a thing that only one person could really do at a time - not like separate features that people can merge and pull little bits from git? Therefore, I was hoping to get it done sometime before givecamp. Unless it's a thing that a bunch of people could sit around one computer and do? Not sure. Thoughts? I started working on it at some point, didn't get very far, then had to stash the changes to get a couple other things done last weekend. But once I un-stashed it and tried to write a migration, something was messed up and then I started upgrading specific gems and upgraded the version of gems to try to fix it. And right now my whole environment is such a hot mess I'm kinda embarrassed for anyone to see it! On the other hand I'm pretty stuck as to what to do about it aside from wiping out the changes I've made and starting over. Which at this point may be the path of least resistance. Anyway - sorry for the rambling - let me know your thoughts on how a Rails 3 upgrade could be a group project! I'd love to hear an opinion on how that could work. :) Gayle From: Kenny Drobnack reply@reply.github.com Gayle, Kenny Drobnack On Saturday, February 18, 2012 at 11:36 AM, Gayle wrote:
Reply to this email directly or view it on GitHub: |
I haven't really experienced upgrading Rails 2 to Rails 3, so I'm not sure how much work it would be. My thinking is there would be some big chunks that would need to be tackled by everyone in a group - things like changes in ActiveRecord that would require everyone working on the same set of source code files. Other pieces would be things where you can divvy up the work - things like certain features using deprecated code… You could file each instance where that happens as a bug that needs to be fixed, and each person working on it could grab a bug & tackle one issue at a time. Kenny Drobnack On Monday, February 20, 2012 at 9:31 AM, Gayle wrote:
|
Give Camp might be sooner that you think... We're having our first organisational meeting tomorrow, going to shoot for end of April. |
I thought Columbus Give Camp was going to be in October this year. Or is that just the big national Give Camp Day? Kenny Drobnack On Tuesday, February 21, 2012 at 3:25 PM, James Bender wrote:
|
That's the national one. They pressure us to do it that day, but it's during college football season and we need more that six people to show up to Give Camp. :) |
Just make sure it's not during an OSU game and you'll be fine ;-) Oh, that's probably every Saturday during that time, isn't it? Kenny Drobnack On Tuesday, February 21, 2012 at 3:40 PM, James Bender wrote:
|
Heh. We actually tried to have it during the bye week a few years ago and the complaint was "Yeah, that's the only week OSU isn't playing, not sure I want to spend it at a Give Camp." :) |
This "issue" has become a "milestone" so I'm closing this issue |
Upgrade from Rails 2 to Rails 3
The text was updated successfully, but these errors were encountered: