Code reviews and bugs silo comments
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Hi,
Just had a discussion with Seb where he complained that he hadn't seen the discussion
of the issues surrounding a change that was going on.
In
Chase and I were discussing the bug and the approach taken to fix it.
Meanwhile Seb, who is subscribed to the package, knew about the bug
https:/
and that there was a branch linked, but didn't know that there was a merge proposal
and some discussion going on in it.
Obviously there is some discussion that should be merge proposal only, such as stylistic
comments about the changed code, but there is some discussion that the bug subscribers
would be interested in. At the very least it would be good for them to be told that there
was a merge proposal.
This is rather nebulous for a bug report, but I wanted to record it so that everyone was
aware of it. It is probably part of a larger discussion about integrating code and bugs
better.
Thanks,
James
| Jonathan Lange (jml) wrote | #1 |
| Changed in launchpad-code: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Martin Pool (mbp) wrote Re: [Bug 556656] Re: Code reviews and bugs silo comments | #2 |
FWIW, Twisted does code reviews in bug comments, partly to avoid the separation of conversations.