On Thu, 2011-05-05 at 15:42 -0400, Hugh Brock wrote:
On Thu, May 05, 2011 at 03:24:30PM -0400, Chris Lalancette wrote:
> On 05/05/11 - 12:11:00PM, Mo Morsi wrote:
> > 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.
>
> Yep, totally agreed.
>
> >
> > 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?
>
> I think our effort would be better spent maintaing a single codebase (on
> Rails 3), and just carrying some Rails 3 RPMs for Fedora 14 for a little
> while. I'm hopeful that once we get it working on F-15, it should be a
> "simple" matter of recompiling the right packages for F-14 to make it
work.
>
Yes, let's *not* fork for rails 2.x, I see no need to take that on.
--H
+1, let's carry the rpms needed for f14 if it is not too much of a
hassle once we make this switch.
-j