Hey all,
More hands are contributing to RSE, and I wanted to shoot around some ideas for managing our WIP packages. I think that everybody pushing to a wip branch with this many members may be reaching its ceiling. I don't know if this is just me (everyone, please chime in!), however I think the following may be things to look out for:
What's the best way to approach these questions?
More hands are contributing to RSE, and I wanted to shoot around some ideas for managing our WIP packages. I think that everybody pushing to a wip branch with this many members may be reaching its ceiling. I don't know if this is just me (everyone, please chime in!), however I think the following may be things to look out for:
- Sometimes more than one head is needed to debug a package because stuff is tedious. People will want to finish a package locally before pushing to WIP -- sending one another snippets isn't a super scalable process (as opposed to collaborating on a new branch for that package). Going back and forth with commits on WIP to debug one thing specifically may also not be the easiest workflow (plus, makes a lot of meaningless history).
- Pushing incomplete packages to WIP may make it difficult for us to "cut" a new release once we are satisfied with what is staged: we need a second round of QA which IMO could be done making PRs on a pkg-by-pkg basis
- Staging packages for merge into WIP would put pressure on completing them, making it easier to depend on other things in WIP with some degree of confidence
- Committing early and making a pull request would allow us to get feedback sooner, and it's feedback that newcomers to autotools like myself very much need!
- WIP repository (now archived)
- A WIP branch on sgug-rse
What's the best way to approach these questions?
Last edited: