Zeckmathederg
commented
1 week ago trunk is meant for development where all the new commits are pushed to. So it will stay as it is. A nightly branch doesn't make too much sense to me. Now stable is where it does sort of make sense. It would be useful if the book actually had releases planned out but it doesn't right now, so it would only be useful if someone obtains the source. It still causes problems as MLFS is rolling release only.
So until MLFS has stable releases, I also won't be making stable releases of GLFS, but I'm not throwing the idea of a stable branch out the window. It'd be for something down the road so I won't implement it right now. I will be keeping this issue open and will be thinking on it, though. Thanks for the suggestion!
Toxikuu
Adding a stable and nightly branch would provide readers with more options, and would improve stability. The nightly branch would also ease the addition of new packages/sections. It would allow readers who desire it access to the latest documentation and packages, and likewise for those who want more stable systems.
Proposed behavior:
The day delays are merely suggestions; feel free to change them according to your liking. This branch scheme could probably be implemented by working on nightly, copying commits >= 14 days old to trunk, >= 28 days old to stable, and be automated with GHA. (Though, note that I'm not familiar with GHA, and there may be superior ways of automating this.)
Thanks!