Explain why we don't want to have a long standing upstream/<feature-branch> #5
Description
See: electronmicroscopy/quantem#178
Problem
We must be mindful of the consequence of having a long-standing feature branch of upstream/<branch> as shown above.
Proposed solution
Adopt a specific branch name such as upstream/pdf upstream/drift instead of upstream/nanobeam and upstream/imaging so that <specific-branch-name> can be merged to upstream/dev iteratively with atomic PRs.
@bobleesj document this
cc for future iteration - @ehrhardtkm