I've set up the tp33 branch. Our git flow is now tp32 merges to tp33 which
in turn merges to master. The master branch has been updated to
3.4.0-SNAPSHOT and the initial java artifacts are currently being deployed.
JIRA has the new 3.4.0 version in it. So...i guess that means 3.4.0 is open
yeah - back to 3 branches for a while. i didn't have any intent to suggest
we EOL 3.2.x at this point. though perhaps in the release after this one we
consider going to a "bugs only" policy on tp32? not really sure yetand
don't think we need to decide that at this juncture.
On Thu, Feb 22,
Will we be maintaining 3 branches or are you planning on EOLing 3.2?
On Wed, Feb 21, 2018 at 10:01 AM, Daniel Kuppitz wrote:
> I was going to start this discussion today. Yesterday I pushed a fix for
> https://issues.apache.org/jira/browse/TINKERPOP-1777, which
I was going to start this discussion today. Yesterday I pushed a fix for
https://issues.apache.org/jira/browse/TINKERPOP-1777, which includes major
breaking changes for a lot of reducing barrier steps, hence a branch for
3.4 which allows breaking changes will be a welcome addition.