Propose changes how-to doc

[activus-d]

This PR adds a new how-to guide, propose-changes.rst, to the Ubuntu Packaging Guide. It provides step-by-step instructions for proposing changes to Ubuntu packages, aimed at both new and experienced contributors.

Related issues

• issue #100 of CODA
• issue #133 of the ubuntu-packaging-guide repository
• A sub-issue in issue #127 — Ubuntu Packaging Guide 2.1 – Extend the Ubuntu Packaging Guide

References used

• Old UPG: Fixing a bug in Ubuntu
• Old UPG (different version): Fixing a bug in Ubuntu
• Ubuntu Maintainer’s Handbook: Fixing a package
• Read the Docs: Ubuntu Packaging Guide

[activus-d]

@dviererbe I haven't edited this PR yet, but I would appreciate a first review. I would also like clarification regarding the final step in the Propose Changes process. Which is the up-to-date process? Fixing a bug in Ubuntu mentions Submitting the fix using submittodebian and debdiff, while the Ubuntu Maintainer’s Handbook suggests a different approach, Merge proposals.

Then, the instructions in Submitting the fix using submittodebian and debdiff appear to be for contributors using pull-lp-source. What are the options available for contributors using other tools, such as apt-get source, git-ubuntu, and pull-pkg?

Finally, in the “Check if the bug is fixed in a newer Ubuntu” section of the draft, I need resources that provide instructions for reviewing changes when users are using apt-get source, pull-lp-source, or pull-pkg.

[julian-klode]

I have some feedback.

[julian-klode]

@dviererbe I haven't edited this PR yet, but I would appreciate a first review. I would also like clarification regarding the final step in the Propose Changes process. Which is the up-to-date process? Fixing a bug in Ubuntu mentions Submitting the fix using submittodebian and debdiff, while the Ubuntu Maintainer’s Handbook suggests a different approach, Merge proposals.

git-ubuntu is prefered.

Then, the instructions in Submitting the fix using submittodebian and debdiff appear to be for contributors using pull-lp-source. What are the options available for contributors using other tools, such as apt-get source, git-ubuntu, and pull-pkg?

submittodebian is correct in all cases.

Finally, in the “Check if the bug is fixed in a newer Ubuntu” section of the draft, I need resources that provide instructions for reviewing changes when users are using apt-get source, pull-lp-source, or pull-pkg.

git-ubuntu is the easiest way, of course you may use pull-lp-source <source package> devel to to find the development release (or another release name instead of devel.

[activus-d]

@dviererbe I haven't edited this PR yet, but I would appreciate a first review. I would also like clarification regarding ...

git-ubuntu is prefered.

Then, the instructions in ...

submittodebian is correct in all cases.

Finally, in the ...

git-ubuntu is the easiest way, of course you may use pull-lp-source <source package> devel to to find the development release (or another release name instead of devel.

Thanks for the review, @julian-klode. I’ve implemented your suggestions, with the exception of one: "I’m not sure if it still works, and it was only functional for Canonical employees." I left a reply asking for your recommendation.