Talk:Branching and Version Control

From LuxCoreRender Wiki
Revision as of 22:34, 31 August 2026 by CodeHD (talk | contribs) (create discussion)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

[CodeHD] First round of commenting:

  • Preliminary considerations look good to me. Not sure the aspects about PyPI will/should really matter in the end, but no harm done in writing them down.
  • In terms of the suggested branching: Previously we had talked about different concepts.
    • what remains identical/similar is having branches like feature/*, etc. In terms of actual branch names, I don't personally care. "Chore" I did not see in guides before, we should add some descriptions of purposes.
    • Different is that we previously talked about separate release preparation branches. I think release processes are still missing as a general category.
    • I am fine with the desciption of main. Essentially, it would remain as-is, i.e. the default branch on GitHub protected against force-push.
  • On long lived branches, your speak of "merging main regularly". I suppose this is supposed to say "rebase"? Otherwise I would expect extra trouble when we work on multiple long-lived branches in parallel which will be merged at different times.