• Immutable Page
• Info
• Attachments
• More Actions: Raw Text Print View Render as Docbook Delete Cache ------------------------ Check Spelling Like Pages Local Site Map ------------------------ Rename Page Delete Page ------------------------ Subscribe User ------------------------ Remove Spam Revert to this revision Package Pages Sync Pages ------------------------ Load Save SlideShow

(See the Wishes page for what this is all about.)

Jamu Kakar <jkakar {_AT_} kakar.ca>

3. Unify bug/code review user experience

   On pretty much all the projects I work on the bug tracker is the
   place where we keep track of things that need to be done to make
   the code or the project better.  Every code-related task starts
   by finding or filing a bug, assigning it to oneself and marking
   it as 'In Progress'.  From there, a branch is created, eventually
   going through a review process before being merged.  At that
   point the bug is closed.  The current separation of merge
   proposals and code reviews from bug reports makes it awkward to
   follow the details of a problem from the initial report,
   discussions about the issue and potential solutions, (typically
   one) proposed branches and associated reviews, to the final
   changes landing.  I would like to be able to look at a bug in my
   web browser and be able to see the whole set of interactions that
   happened around it, without needing to jump around from the bug
   to individual merge proposals.