Hi Daniel, sorry for the delayed response. As for fixing-a-bug.rst, here are my thoughts:
I added Figuring out what to fix, which I think is useful information at that point. In the old version it says "If you know which source package contains the code..." but what if you don't know? That's what I covered in the new section. I guess you're suggesting that the 'bzr branch' commands in the old Get the code section should be restored, instead of moved to the branching.rst file? What do you think about adding back a section in the new version that shows a "quick teaser" for how to get the branch? The main article can still be in branching.rst, but I can add back most of the text from the old Get the code section. The Work on a fix section is largely the same in both versions. Testing the fix, Documenting the fix, and Committing the fix still do feel better split out, otherwise fixing-a-bug.rst will get to be too long I think. Or do you still feel strongly that those should be added back to fixing-a-bug.rst? Tomorrow, I can push an updated branch based on your response. Cheers! -- https://code.launchpad.net/~barry/ubuntu-packaging-guide/udd/+merge/48685 Your team Ubuntu Packaging Guide Team is requested to review the proposed merge of lp:~barry/ubuntu-packaging-guide/udd into lp:ubuntu-packaging-guide. _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-packaging-guide-team Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-packaging-guide-team More help : https://help.launchpad.net/ListHelp
