For my pilot shift I focused on starting work on a patch pilot manual, as discussed and tasked to me at the 25 Aug 2023 git-ubuntu feedback session. At this initial point the work is less of a manual and more of a semi-cohesive set of tips but hopefully useful none-the-less and maybe something others can use to hang additional docs on.
Due to time limitation I focused all my time on content, rather than formatting, and other than making sure `rstcheck` passes successfully on it I didn't verify the formatting validity. That'd be a good follow-on task.
There are also a few topics left empty. I think they're necessary questions for considering the document minimally useful, however didn't have time to fill them in. They're also left as suggested follow-on work for now.
I also can't say if this is the ideal place to house the document; again my goal was more about content generation. Feel free to move this or rename it to fit better into the overall documentation structure.
I'd like to highlight the section that outlines a paint-by-numbers workflow for mechanically converting a debdiff into a proper git-ubuntu branch. While much of the rest of this doc is rehashing info from elsewhere, this bit is new and I suspect quite pertinent to patch pilot as the initiative strives to move towards using a more git-ubuntu oriented workflow.
Anyway, hope this is helpful.
PASSED: Continuous integration, rev:8b8823937a3
https:/
Executed test runs:
SUCCESS: VM Setup
SUCCESS: Build
SUCCESS: VM Reset
SUCCESS: Unit Tests
IN_PROGRESS: Declarative: Post Actions
Click here to trigger a rebuild:
https:/