{"thread":{"id":"12504","subject":"Bug-tracking tools that handle branch/merge/etc","startedAt":"2008-03-04T22:09:03Z","lastAt":"2008-03-04T22:24:21Z","messageCount":2,"participants":["Thomas Harning","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"71002","messageId":"20080304170903.7b029fc3@gmail.com","threadId":"12504","inReplyTo":null,"subject":"Bug-tracking tools that handle branch/merge/etc","fromName":"Thomas Harning","fromEmail":"harningt@gmail.com","sentAt":"2008-03-04T22:09:03Z","receivedAt":"2008-03-04T22:09:03Z","isPatch":false,"sender":{"key":"harningt@gmail.com","avatar":"https://gravatar.com/avatar/a79ddd43da8c8f1f899cd75b7b95cc5f3b2ba5643400468988b1a12c86b75d08?d=mp&s=160"},"body":"Partly referring back to the discussion last June\n(http://article.gmane.org/gmane.comp.version-control.git/49734)...  has\nthere been any developments in the area of a BTS that can grok GIT in a\nsane way?\n\nMain concept I see as important for a BTS grokking git:\n * Capability of following branches/merges in a way that\n   you can see a list of bugs that affect a branch at any point\n   in time.\n\nNiceties include:\n * The ability to 'distribute' this so bug tracking is as disconnected\n   as coding itself (great for airplane-trip coding sessions)\n * Ability to watch incoming commits (suppose the BTS can 'pull' from\n   various sources on occasion) for messages marking a bug as\n   in-progress/fixed/re-opened/etc.\n * Local-application GUI integration... ex: gitk/git-gui + BT\n"},{"id":"71006","messageId":"m3ve42gmae.fsf@localhost.localdomain","threadId":"12504","inReplyTo":"20080304170903.7b029fc3@gmail.com","subject":"Re: Bug-tracking tools that handle branch/merge/etc","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2008-03-04T22:24:21Z","receivedAt":"2008-03-04T22:24:21Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Thomas Harning <harningt@gmail.com> writes:\n\n> Partly referring back to the discussion last June\n> (http://article.gmane.org/gmane.comp.version-control.git/49734)...  has\n> there been any developments in the area of a BTS that can grok GIT in a\n> sane way?\n\nUnless you count work-in-progress Grit (http://git.madism.org/?p=grit.git)\nI think the answer is no. The 'after the fact commit annotation' aka\ngit-notes are also as far as I can see abandoned.\n\nhttp://git.or.cz/gitwiki/InterfacesFrontendsAndTools#head-3a410db622d55b4dd88d91437d2c953f6b730542\n\n> Main concept I see as important for a BTS grokking git:\n>  * Capability of following branches/merges in a way that\n>    you can see a list of bugs that affect a branch at any point\n>    in time.\n> \n> Niceties include:\n>  * The ability to 'distribute' this so bug tracking is as disconnected\n>    as coding itself (great for airplane-trip coding sessions)\n>  * Ability to watch incoming commits (suppose the BTS can 'pull' from\n>    various sources on occasion) for messages marking a bug as\n>    in-progress/fixed/re-opened/etc.\n>  * Local-application GUI integration... ex: gitk/git-gui + BT\n\nBTW. you can put it in SoC2008Ideas as a project for Google Summer of\nCode 2008... then try to find a mentor for this project ;-)\n\nhttp://git.or.cz/gitwiki/SoC2008Ideas\n\n-- \nJakub Narebski\nPoland\nShadeHawk on #git\n"}]}