On 05/05/2011 11:30 AM, Matt Wagner wrote:
Hi,
In between sprints I spent a little bit of time looking at what it would
take to get Conductor to run on Fedora 15. The most obvious change is
that Fedora 15 ships with Rails 3.
My effort to get things running was very incomplete and it's not yet in a
working state. But now that I'm no longer working on it, I wanted to
mention that I pushed a 'rails3' topic branch so others can pick it up
when the mood strikes / time allows.
Most of Mo's patches from December[1] won't apply because the project
has changed so much. All but 6/8 and 7/8 have been applied, though
applying the patches is largely a manual effort. There is also other
work that will need doing, including updating several versions of gems
that don't seem to be compatible with Rails 3.
I have notes on my efforts at
http://aeolusproject.org/page/Rails_3_Migration
Redmine tasks #190 and #1435 should track the remaining work that I'm
aware of.
[1]
https://fedorahosted.org/pipermail/deltacloud-devel/2010-December/thread....
-- Matt
_______________________________________________
aeolus-devel mailing list
aeolus-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/aeolus-devel
Hey thanks for getting the ball rolling on this again. In addition to
the patches,here are all the exact changes that had to be made to the
web app itself to get things working against Rails 3:
http://mo.morsi.org/blog/node/331
As you said, in addition to updating the patches, we need to update the
packages in Fedora that we depend on to be compatible with Rails 3. I
already updated a couple of the major ones (haml, authlogic) this past
month, but there are several more togo. All in all the gems which we
depend on are represented in our conductor config and spec file:
http://git.fedorahosted.org/git/?p=aeolus/conductor.git;a=blob;f=src/conf...
http://git.fedorahosted.org/git/?p=aeolus/conductor.git;a=blob;f=aeolus-c...
Since the F15 release is coming up, we should allocate some time in our
next sprint to evaluating exactly what needs TBD in terms of packages
that need to be updated and getting the patchset back in sync w/ the
latest codebase.
We should push for very quick adoption once this is all done, else we
are going to continue spinning our wheels, needing to continuously
update the patches every time a commit is pushed to the repo.
Of course once the patches are pushed, the app won't work against rails
2 anymore, but we can tag the last commit which it does and fork a
maintenance branch off that, if we want to continue supporting conductor
on F14.
Thoughts?
-Mo