Folks, Now that CURATOR-3.0 is master, how should we deal with keeping CURATOR-2.0 in sync. It's no longer possible to do simple merges. Should we cherry-pick changes into CURATOR-2.0? Should we require separate PRs for changes to each branch?
Scott, you're our resident git expert. Any best practices to apply here? -Jordan
