tag:blogger.com,1999:blog-7854892290437883216.post14311898070641827..comments2023-04-07T23:51:07.346+12:00Comments on How Bazaar: Don't wait for perfectionTim Penhey (thumper)http://www.blogger.com/profile/09872376538882273724noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7854892290437883216.post-24485372187808494732009-11-16T20:21:15.598+13:002009-11-16T20:21:15.598+13:00Well, there are two slightly related changes that ...Well, there are two slightly related changes that have either happened or happening.<br /><br />Firstly the diffs shown with the code review is updated when the branch is pushed to. One change I'd like to add here is extra notification to the subscribers that the branch has changed.<br /><br />The second is showing the conversation of the superseded proposals on the subsequent proposals, but not allowing replies to the comments. New comments get added to the current review. We'll probably have some extra indication (like background colour/footer info) on the older comments.Tim Penhey (thumper)https://www.blogger.com/profile/09872376538882273724noreply@blogger.comtag:blogger.com,1999:blog-7854892290437883216.post-25484353838145964522009-11-16T20:11:47.287+13:002009-11-16T20:11:47.287+13:00This sounds interesting to me. With Bazaar moving ...This sounds interesting to me. With Bazaar moving from BundleBuggy to launchpad merge-proposals & code-reviews, this is something I noticed:<br />Having the review-process tightly linked to the merge-proposals causes the review-thread to become quite disjointed when resubmitting your branch. Hopefully this line of thinking would improve this so it can be easier to follow review comments back to comments made on previous proposals in the same review thread (which is needed for context, like to understand why the branch was re-subitted in the first place).Anonymoushttps://www.blogger.com/profile/06939512410991481694noreply@blogger.com