On 10/2/07, Lance Carlson <[EMAIL PROTECTED]> wrote:
> Are you saying Rspec was never meant to work with edge rails? I've

David wasn't saying that. We cannot travel back in time and make 1.0.8
work with today's rails.
But we can (and are doing) our best to make RSpec trunk work with edge
Rails trunk.

Aslak

> been using Rspec with edge rails and I've got it to work for the most
> part (even though i seem to have problems with some of the new
> syntactic sugar). Is this because rspec somehow isn't expecting rails
> 2.0 esk code?
>
> On 10/2/07, David Chelimsky <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> > For those of you checking out the Rails 2.0 preview release:
> >
> > RSpec-1.0.8 does not support Rails 2.0.
> >
> > Unfortunately, we're in the middle of some big changes to the
> > internals in trunk and won't be in a position to do a release for
> > another week or so. Therefore, if you are using the Rails 2.0 preview,
> > you'll need to use the RSpec trunk.
> >
> > Additionally, right now there is at least one known issue related to
> > Rails 2.0 and RSpec - however it was reported on the list and not in
> > the tracker. Please report bugs to the tracker. It's fine to talk
> > about them on the lists first, but they will almost certainly not get
> > addressed in RSpec unless/until you report them in the tracker. And,
> > of course, patches will get addressed faster than bug reports w/ no
> > solutions.
> >
> > http://rspec.rubyforge.org/community/contribute.html
> >
> > http://rubyforge.org/tracker/?group_id=797
> >
> > Cheers,
> > David
> > _______________________________________________
> > rspec-users mailing list
> > rspec-users@rubyforge.org
> > http://rubyforge.org/mailman/listinfo/rspec-users
> >
> _______________________________________________
> rspec-users mailing list
> rspec-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users

Reply via email to