Hi all,

Now that I've actually *used* the Trac Ticket system, I feel I can
now provide comment as to its functionality. I never did provide
comments about functionality before, as I had not used it, I only
offered opinion on the reasons for changing and the method used to
implement Trac.

I don't expect the following notes to be anything other than
conversation items. I am not asking to go go back to Bugzilla, nor
do I think we should. These items are mentioned in hopes that
there can be fixes or enhancements to Trac.

1. Time-wise I feel that Trac and Bugzilla are about the same. I
don't see any real appreciable difference (or speed-up which was
claimed) using either one. There are still tremendous (sometimes 20
to 30 second) delays trying to move from one screen to another. I
am disappointed here.

2. Bugzilla, functionality-wise seems to be better.

  a) I liked the field in BZ that was available for a relevant URL.

  b) The color-coding doesn't do anything for me. I can't see much
     difference in Trac or Bugzilla in this respect.

  c) I would prefer the default to be a "task" rather than a
     "defect" when entering a new bug in Trac. Most bugs (in BLFS,
     anyway) are version increments, which should not be classified
     as defects.

  d) I don't like how all the bugs moved from BZ to Trac that are
     for version increments are marked "defect"

  e) I don't like (and this is the reason I created this message, as
     I feel this is a large shortcoming) that you cannot reference
     bug numbers when marking duplicates, and you cannot reference
     bug number dependencies (I realize it could be done manually,
     however, I liked the automated system in BZ.

-- 
Randy

rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3]
[GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686]
10:57:00 up 140 days, 20:21, 3 users, load average: 0.15, 0.21, 0.18
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to