0ea096ae23
Move away from using staging and core-updates, and make the strategy independant of branch names. Keep the 300 dependent threshold for changes to master, as I don't have any specific reason to change this. Most importantly, require using guix-patches issues to coordinate merging of the branches, as I think that'll address the key issues that have shown up recently where it's been unclear which branch should be merged next. * doc/contributing.texi (Submitting Patches): Move the branching strategy to a new Managing Patches and Branches section. (Managing Patches and Branches): New section. (Commit Policy): Simplify through referencing the new Managing Patches and Branches section. Signed-off-by: Christopher Baines <mail@cbaines.net> |
||
|---|---|---|
| .. | ||
| images | ||
| build.scm | ||
| contributing.texi | ||
| environment-gdb.scm | ||
| fdl-1.3.texi | ||
| guix-cookbook.texi | ||
| guix.texi | ||
| he-config-bare-bones.scm | ||
| htmlxref.cnf | ||
| local.mk | ||
| package-hello.json | ||
| package-hello.scm | ||