On Thu, Mar 4, 2010 at 1:58 AM, Aslak Hellesøy <aslak.hellesoy at gmail.com> wrote:
>>>> Hey all,
>>>> rspec-rails-2 will only work with rails-3 (not rails-2). My suspicion
>> is that once rspec-2 is out, folks are going to want to start using it
>> with their existing rails-2 projects (because it offers some sweet new
>> goodness that you won't want to live without).
>>>> Would anybody be interested in writing and maintaining and
>> rspec-2-rails-2 gem? This would be a separate code-base from
>> rspec-rails, but we could keep the repo under the new rspec github
>> user (http://github.com/rspec) provided that it is generally accepted
>> and used by the community.
>>> FWIW, cucumber-rails supports both Rails2 and Rails3. If someone picks up
> the challenge it might be worthwhile to study the codebase. It uses some
> smart tricks to support both in the same codebase, without too much
> duplication.
>> Maybe supporting both Rails2 and Rails3 in rspec-rails is a smaller effort
> than maintaining 2 gems?
I'm certainly open to the idea, but don't have cycles to investigate
it myself. I'd welcome someone taking on this cause and submitting
patches. Anyone interested?
>> Aslak
>>>> Let me know if you're interested, or if you have any concerns about
>> this approach.
>>>> Cheers,
>> David
>> _______________________________________________
>> rspec-users mailing list
>>rspec-users at rubyforge.org>>http://rubyforge.org/mailman/listinfo/rspec-users>> _______________________________________________
> rspec-users mailing list
>rspec-users at rubyforge.org>http://rubyforge.org/mailman/listinfo/rspec-users>