Changes between Version 18 and Version 19 of TracDev/DevelopmentWorkflow

Timestamp:

Mar 1, 2023, 9:58:47 AM (14 months ago)

Author:

figaro

Comment:

Cosmetic changes (still needs work as travis reference needs to be removed at some point)

TracDev/DevelopmentWorkflow

@@ -5 +5 @@
 == Initial code review
 
-Except for trivial fixes, it's usually a good idea to start with a patch or an experimental branch, to provide some visibility of the changes to the other contributors.
+Except for trivial fixes, it's usually a good idea to start with a patch or an experimental branch, to provide some visibility of the changes to the other contributors. Create a patch as a [t:TracDev/SubmittingPatches#Makethepatch unified diff].
 
 A patch is always attached to a ticket. If there is no ticket, then create one and attach the patch to it.
@@ -40 +40 @@
 === Skipping Build
 
-If you are confident the CI tests don't need to be
-run for this commit (e.g. a documentation change),
-add [[https://docs.travis-ci.com/user/customizing-the-build/#skipping-a-build|"[skip ci]"]].
+If you are confident the continuous integration tests don't need to be run for this commit (e.g. a documentation change), add [[https://docs.travis-ci.com/user/customizing-the-build/#skipping-a-build|"[skip ci]"]].
 
 === References
@@ -56 +54 @@
 While this pattern of //forward porting// makes it easy to merge all pending changes, in practice we cherry-pick changes as they are committed in order to keep all branches in sync and prevent pending changes from accumulating on a branch. Multiple changesets can be cherry-picked in a single merge command using a comma-separated list of changesets: `-c 15407,15409`.
 
-Here's a walk through example. We start by hacking on [source:branches/0.12-stable 0.12-stable]:
+As a walk-through example, we start by developing on [source:branches/0.12-stable 0.12-stable]:
 {{{#!sh
 0.12-stable$ ed trac/attachment.py # or your other favorite editor