On Wed, Oct 1, 2008 at 10:32 AM, Pat Maddox <[EMAIL PROTECTED]> wrote: > Ashley Moran <[EMAIL PROTECTED]> writes: > >> On 1 Oct 2008, at 15:23, Pat Maddox wrote: >> >>> I think this may be a bug that I introduced recently. Fortunately I >>> also think someone already wrote a patch :) Check out >>> http://rspec.lighthouseapp.com/projects/5645/tickets/548 and see if it >>> solves your problem. >> >> Aha! That's it. >> >> That's a pretty bad bug though! Will there be an RSpec 1.1.6 soon to >> patch it? > > I don't know, we'll late David determine how critical it is and whether > it warrants a new release. > > fwiw, I've run that code against several rails apps and open source > projects with no problems. So while I agree that it's a nasty little > bug, I'm not sure how often it comes up in practice? Maybe we can knock > out a bunch of outstanding bug reports in the next couple days and push > out 1.1.6.
There were a couple of other bugs introduced in 1.1.5 so I would like to get out a 1.1.6 very soon. Probably over the weekend if we can get them all fixed. Cheers, David > > Pat > _______________________________________________ > rspec-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/rspec-users > _______________________________________________ rspec-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/rspec-users
