Our policy is to target the lowest still active release branch possible. We'll then merge a PR into that branch and afterwards merge that release branch into higher release branches and ultimately master. That way, a fix lands in all possible release branches. In your case, `3.3-dev` should be the correct release branch as it already contains that code and because we stopped working on the `3.2-dev` branch. @spmallette: Should we maybe rename the inactive release branches (`3.0-dev` - `3.2-dev`) to avoid confusion?
[ Full content available at: https://github.com/apache/tinkerpop/pull/1256 ] This message was relayed via gitbox.apache.org for [email protected]
