I was reviewing documentation in preparation for release and learned that it seems that we already made this decision somewhere prior to us starting on 3.2.10 because our docs already reflect it:
http://tinkerpop.apache.org/docs/current/dev/developer/#branches Not sure how that went off the rails, but let's make sure we don't accidentally go down the path of setting up for unnecessary development on tp32 in this next cycle. Let's reserve tp32 for only the worst bugs and generally leave documentation alone. On Sat, Oct 6, 2018 at 6:34 AM Stephen Mallette <[email protected]> wrote: > We're going on the 11th release on the 3.2.x line. Not a bad run. I don't > think that we need to close the tp32 branch but I do think that it might be > time to reserve changes there for bug fixes only. I'm thinking we focus on > the 3.3.x and 3.4.x lines going forward. > > I think we came to this conclusion once before, but I can't seem to find > the thread. Happy to hear any thoughts on the matter - unless there are > objections let's head down this path going forward. >
