aboutsummaryrefslogtreecommitdiff
path: root/etc
diff options
context:
space:
mode:
authorChristopher Baines <mail@cbaines.net>2022-11-23 10:37:11 +0000
committerChristopher Baines <mail@cbaines.net>2022-12-12 10:49:30 +0000
commitbe0592f3417d9b8f1d34b93e11a0ef345a59fff4 (patch)
treeda524c8c6646af37056895ec5ca6a07dc931eaf0 /etc
parentf76ed96f934fc83bb0f974396941c6a90a90e9fc (diff)
downloadguix-commit-policy-tweaks.tar
guix-commit-policy-tweaks.tar.gz
doc: contributing: Tweak the Commit Policy.commit-policy-tweaks
Add more examples of when it can be appropriate to push changes without review, as I think this can be appropriate in the case of trivial changes (as mentioned before), but also non-trivial fixes. No longer suggest pushing simple new packages or package upgrades (that don't cause lots of rebuilds) without sending to guix-patches. Now there's some automation for testing changes sent to guix-patches, sending changes there before pushing can mean that more rigorous testing takes place and help speed up substitutes becoming available. This is true, even if no human review takes place. Only suggest waiting one week for review for simpler changes, wait two weeks for more significant changes. Also, reorder some of the information in this section so it's grouped together better. * doc/contributing.texi (Commit Policy): Tweak.
Diffstat (limited to 'etc')
0 files changed, 0 insertions, 0 deletions