[rspec-devel] Rails: tracking Edge or Stable release? (found bug on edge)
david at davelee.com.au
Sat Oct 7 20:49:40 EDT 2006
Sounds like a pretty fair deal, thanks.
I'll use stable Rails for now. Maybe I'll learn enough about RSpec's
internals in the meantime that if / when i need to use edge I can do
something more useful than just scream when i see a bug.
Look forward to seeing it come along.
On 08/10/2006, at 5:10 AM, David Chelimsky wrote:
> While rspec core is fairly stable at this point, rspec_on_rails has a
> way to go and will remain volitile for a little bit. That said, feel
> free to raise any bugs you wish. Even if we don't get to them right
> away we want to know what's going on, and in the long run we want
> rspec_on_rails to be a flat out better choice than test/unit for those
> interested in BDD and even those TDD'ers who just long for better
> separation between model, controller and view specs.
> As far as edge rails is concerned, we don't have a formal policy about
> this yet but we should have one before we release 1.0 (which I am
> hoping will happen before the end of the year). My current thinking is
> that, given that all of the committers are fortunate to be working
> full time jobs, we'll likely not commit to keeping up w/ edge rails,
> but that we'll always try to support the latest rails release as of
> our release. That seems fair and feasible to me.
>> thanks for the great tool, all involved
> Thanks for using it and expressing your interest in it.
>> rspec-devel mailing list
>> rspec-devel at rubyforge.org
> rspec-devel mailing list
> rspec-devel at rubyforge.org
More information about the rspec-devel