Page 1 of 1

Why updating trac is important

Posted: Sun Jul 01, 2007 7:44 pm
by shirish
Hi all,
The problem with trac 0.10 is it doesn't send you reminders or replies when somebody does respond to your bug. This makes it difficult for the user to know that somebody did respond to his bug & now its turn. For e.g. http://dev.deluge-torrent.org/ticket/382 . Now markybob did the right thing by first asking the user (in this case, me) and after finding no response from me closing the thread/bug-report. There is difference of 2 days which in the right circumstances are more than enough to see & respond the bug but alas due to trac failure couldn't do so. I dunno how many useful bug-reports had to be closed for this & its not that the developers should send a mail or something. Its the BTS (Bug Tracking System) which should send a reply as & when its written (provided the user has given the details).

Re: Why updating trac is important

Posted: Mon Jul 02, 2007 3:51 am
by shirish
Sorry couldn't complete what I had in mind as electricity went out yesterday. (The plight of being in a developing country). Anyways I have been also being doing tickets on other trac & trac 0.10.3 & above support this. You can try out the same at the official trac http://trac.edgewall.org/newticket . Btw trac 0.11 would be out in 6 days so perhaps zach can put that one on his personal machine & see how it feels and if he feels it appropriate then upgrade the same. It would be better if we had a system where communication mis-matches are at a lower level. And yes, here is slightly premature release notes. http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/0.11

Edit: Another project which uses trac features to its fullest extent, http://developer.pidgin.im/timeline http://developer.pidgin.im/about

Re: Why updating trac is important

Posted: Mon Jul 02, 2007 9:36 pm
by jorge.vargas
shirish wrote:Hi all,
The problem with trac 0.10 is it doesn't send you reminders or replies when somebody does respond to your bug.
umm and I though that CC field in the ticket was there for something.

maybe the problem is that deluge's trac has no mail configuration which is very different