Jeremy Kemper wrote:
Rob Sanheim wrote:
Trac has been updated on the new box (to 0.10dev) and includes a spam
filter, so we have a tool to combat that annoyance. Also, the RSS feed
includes comments on tickets so older tickets under development won't
disappear from the radar. Anything else we can do to lube the process?
Trac lint sounds like a great idea.
Does this mean that adding new tickets now works, and all those issues
are sorted out?
It would be nice to know what the problem with Trac was, and how it was
I'm working on a large project with all user stories, developer stories,
engineering tasks and defects in Trac - it would be a disaster if it
stopped working for us.
Hey Justin - Trac has worked great on the whole, but needs care and feeding.
Unless a ticket is quickly resolved it will drift off the timeline (the RSS
feed is how most keep tabs on Trac) and out of memory.
So it works well for tickets that are poor or wonderful, but not so well for
your average ticket which needs work (usually tests or docs). You had to
add yourself to the CC field on every ticket you wanted to participate in.
Just doesn't work. This is why I've been resolving tickets as 'wontfix' and
'invalid': the resolution shows up in the timeline so the ticket gets its
share of fresh eyeballs.
By having all ticket activity show up on the timeline, including comments
and new attachments, our bread & butter tickets can compete for attention
Hi Jeremy - that all sounds eminently sensible.
I was really asking about what happened to make the Rails Trac completely unusable for days on end. Was it lack of capacity, misconfiguration, a bug, or what? It's scary to see a key piece of infrastructure fail and take some time to fix.