On Wed, Feb 14, at 12:45 Randy McMurchy wrote: > Hi all, > > Sorry to be a stick-in-the-mud, and perhaps it's just me, but I don't > like this "lump everything in one ticket" idea (using the BLFS-6.2.0 > Text Changes ticket as an example). I find it difficult (if not > impossible) to figure out: > > 1. What has been taken care of? > 2. What is still under discussion? > 3. Who is working on what > 4. What is still open?
Well...the technology is not enough (the current tracking system design,is boring and monolithic). What I mean is that -and I believe we all agree in that point- the idea to collect all the patches and the reports of these kind of things in one place,is actually good and brought some results. And quite possible,some more patches/reports from the community in the future. What I would expect (at least in the future), from a bug-tracking technology is some kind of sub-tickets/threads. Maybe an arrow that could click on it and you could bring up the collapsed sub-ticket,for comments/replies and actions like closing. Somehow,how the folding works in vim. ":h folding" to see what I mean. Example. report a ----- here it goes the discussion/status of the a report. report b ----- --||-- b --||--. etc... How many answers could wait from such a report.One? Two? And probably an indicator that you could see that the (a) report is either closed or still open,could make the navigation of the ticket easier. > > I'd prefer if we go back to the tried-and-true method of opening a > ticket when there's an issue, and closing it when it is fixed. Perhaps > I'm just old-fashioned. > I still like the idea,the implementation is the problem. We need some innovation or maybe to bring up some old-proved-to-work ways in a modern release. For your information,I could happily live and develop,with the only tool,the various mailing lists... and vim. So I guess I more old-fashioned than you are. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
