The mental weight of open pull requests
I just merged two PRs into RavenDB, and for the first time in a while, I got this beautiful number:
For the past few months, we have been working on several long running features, graph queries being the most obvious example. We are now at a stage where we are ready to pull all this work together, which mean that all the long running feature branches (and the discussion about them in the PR) is merged to the next release branch.
And for a while, I can luxuriate in that wonderful feeling.
Comments
How do you manage multiple long-running branches? For example, you've got your vNext branch where you are putting bug fixes and merging smaller new features regularly, but then you've also got LongRunningFeature1 and LongRunningFeature2. Both of those branches will be get changes made in vNext regularly, but changes in LongRunningFeature1 won't get to LongRunningFeature2 until LongRunningFeature1 gets merged into vNext and then vNext gets merged into LongRunningFeature2.
Chris, This is a great question, I wrote a full post about this, which you can read here: https://ayende.com/blog/184803-A/managing-a-multi-version-project?key=69efc4b4ba464d5ab54cfa36bca2b89c
Comment preview