git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC] git integrated bugtracking

From
Yann Dirson <ydirson@altern.org>
Date
Jun 3, 2007, 20:31 UTC
Message-ID
<20070603203147.GH6992@nan92-1-81-57-214-146.fbx.proxad.net>
In-Reply-To
<Pine.LNX.4.64.0706031203220.6705@asgard.lang.hm>
On Sun, Jun 03, 2007 at 12:07:44PM -0700, david@lang.hm wrote:
Show 11 quoted lines
> >>1. bug number doesn't work well in a distributed environment
> >
> > Sure, SCM revisions either. But git solved that once, I don't see why
> >the solution found at that time would be less of a solution now :)
> 
> git's tracking of revisions works becouse it's tracking the content, it 
> doesn't care _how_ the content got that way, if it's the same it's the 
> same and will have the same hash.
> 
> with bugs the reports aren't the same so you can use the sha1 to track a 
> particular entry/tag/comment but not to identify the bug itself

Do you see any problem with taking as bug id the hash of the first entry submitted ? Just like in a classical BTS, the bug id gets allocated at submussion time. Further informations then get associated with the initial report - here that would problably translate into the initial report being an annotation to a source commit, and further information being annotations to the initial annotation.

> fine grained categorization is something that takes place long after the 
> bug is reported, users don't know how to correctly categorize bugs any 
> more then they know what code caused the bug.
Is that a problem ?
Show 8 quoted lines
> > My experience with bugtracking is that the most efficient way to deal
> >it is to let the programmer in charge of the responsible module deal
> >with those bugs. What programmer aren't willing to do is the triaging,
> >and pulling the bugs off a distant database/UI/.. off something that
> >isn't in their usual workflow.
> 
> this only works if someone goes to the work to send the bugs to the right 
> programmer. in many cases this is non-trivial.

This is he work of a QA team, and although it is not as common in the Free Software world as it should be, there are people willing to do the job. This discussion is about giving these people a better tool to help them focus on the tasks where a human being is really needed.

Best regards,
-- 
Yann.
Previous: david@lang.hmNext: Yann Dirson
Message 13 of 46 in “[RFC] git integrated bugtracking”
  1. Pierre HabouzitJun 3, 2007
  2. Yann DirsonJun 3, 2007
  3. Pierre HabouzitJun 3, 2007
  4. Michael PooleJun 3, 2007
  5. Pierre HabouzitJun 3, 2007
  6. Johan HerlandJun 3, 2007
  7. Pierre HabouzitJun 3, 2007
  8. Matthieu MoyJun 3, 2007
  9. Pierre HabouzitJun 3, 2007
  10. david@lang.hmJun 3, 2007
  11. Pierre HabouzitJun 3, 2007
  12. david@lang.hmJun 3, 2007
  13. Yann DirsonJun 3, 2007
  14. Yann DirsonJun 3, 2007
  15. Yann DirsonJun 3, 2007
  16. Pierre HabouzitJun 3, 2007
  17. Yann DirsonJun 4, 2007
  18. Pierre HabouzitJun 4, 2007
  19. Linus TorvaldsJun 3, 2007
  20. Pierre HabouzitJun 3, 2007
  21. Martin WaitzJun 3, 2007
  22. Rogan DawesJun 4, 2007
  23. Yann DirsonJun 3, 2007
  24. Pierre HabouzitJun 3, 2007
  25. Pierre HabouzitJun 9, 2007
  26. Jakub NarebskiJun 9, 2007
  27. Daniel BarkalowJun 10, 2007
  28. Johannes SchindelinJun 10, 2007
  29. Martin LanghoffJun 10, 2007
  30. Junio C HamanoJun 10, 2007
  31. Martin LanghoffJun 10, 2007
  32. Pierre HabouzitJun 10, 2007
  33. Martin LanghoffJun 10, 2007
  34. Pierre HabouzitJun 11, 2007
  35. Martin LanghoffJun 11, 2007
  36. Jan HudecJun 10, 2007
  37. Jon LoeligerJun 11, 2007
  38. Guilhem BonnefilleJun 12, 2007
  39. Jan HudecJun 10, 2007
  40. Martin LanghoffJun 10, 2007
  41. Jan HudecJun 10, 2007
  42. Matthieu MoyJun 10, 2007
  43. Pierre HabouzitJun 10, 2007
  44. Pierre HabouzitJun 10, 2007
  45. Pierre HabouzitJun 10, 2007
  46. Rogan DawesJun 4, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.