I agree with you that the Rubyforge tracker isn't the ideal tracker, but
it's integrated in Rubyforge, so that's a plus. Setting up Trac might cost a
great deal of time, and will it really benefit the development process?
If we're talking about Trac, we should also put lighthouse into the
consideration.
On 9/6/07, Michael Klishin <michael.s.klishin.lists at gmail.com> wrote:
>> Guys,
>> I'm trying to follow RSpec development but constantly find out that I
> have no time to read all emails from dev list and read commit logs /
> source changes.
>> Maybe it makes sense to set up Trac? Beside being a bit better at
> tracking requests and bug reports it has Timeline and Roadmap that save
> huge amount of time compared to SVN logs and source digging.
>> WDYT?
>> --
> MK
> _______________________________________________
> rspec-devel mailing list
>rspec-devel at rubyforge.org>http://rubyforge.org/mailman/listinfo/rspec-devel>-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/rspec-devel/attachments/20070906/757e42dd/attachment.html