Re: Code Freeze 3.2.3/3.1.5

I created 3.2.4 and 3.1.6 in JIRA and transferred all unresolved issues from 3.2.3 to 3.2.4 (there were no unresolved issues on 3.1.5). There were a lot of issues to transfer and given that we are heading down the 3.3.0 route, I wonder how many of those issues will actually close for 3.2.4. If you

Re: Code Freeze 3.2.3/3.1.5

Here's the fix: $ git diff bin/validate-distribution.sh diff --git a/bin/validate-distribution.sh b/bin/validate-distribution.sh index 4daaf47..2148610 100755 --- a/bin/validate-distribution.sh +++ b/bin/validate-distribution.sh @@ -117,11 +117,11 @@ if [ "${TYPE}" = "SOURCE" ]; then cd

Re: Code Freeze 3.2.3/3.1.5

You've probably noted the VOTE thread is out for 3.2.3 - note that bin/validate-distribution.sh works, but I noticed it generates a bit of junk logging around python output. Not sure what that's all about. I've sent a note to kuppitz about it. At least it still works - you just have to ignore that

Re: Code Freeze 3.2.3/3.1.5

I got delayed on TINKERPOP-1511 - trying to get the release put together now. On Sun, Oct 16, 2016 at 8:38 PM, Ted Wilmes wrote: > No problem, thanks for the heads up. I just had been doing some prep and > dry runs. I added it to the changelog too and I'll get things

Re: Code Freeze 3.2.3/3.1.5

No problem, thanks for the heads up. I just had been doing some prep and dry runs. I added it to the changelog too and I'll get things finished up tomorrow. --Ted On Sun, Oct 16, 2016 at 3:36 PM, Stephen Mallette wrote: > da > > ted - i just fixed this on tp31: > >

Re: Code Freeze 3.2.3/3.1.5

da ted - i just fixed this on tp31: https://issues.apache.org/jira/browse/TINKERPOP-1512 sorry - i realized too late that you had done some work on firming up that branch for release. hope you don't need to do too much re-work as a result of my push. On Sun, Oct 16, 2016 at 11:14 AM,

Re: Code Freeze 3.2.3/3.1.5

I think TINKERPOP-1511 should be fixed in 3.2.3. On Fri, Oct 14, 2016 at 10:09 PM, Ted Wilmes wrote: > A fresh 3.1.5-SNAPSHOT has been deployed along with the docs. > > --Ted > > > > On Fri, Oct 14, 2016 at 2:10 PM,

Re: Code Freeze 3.2.3/3.1.5

I just upgraded and things are looking good. Cheers Pieter On 14/10/2016 20:50, Stephen Mallette wrote: > It's been fairly quiet on this thread for this release for some reason. I > assume that can only mean that this is to be the best release ever! > > I just published the latest

Re: Code Freeze 3.2.3/3.1.5

It's been fairly quiet on this thread for this release for some reason. I assume that can only mean that this is to be the best release ever! I just published the latest 3.2.3-SNAPSHOT again to Apache Snapshots Repository and also republished the docs:

Re: Code Freeze 3.2.3/3.1.5

Cool, sounds good. I'll get a 3.1.5 snapshot published and then prep for vote. --Ted On Fri, Oct 14, 2016 at 1:50 PM, Stephen Mallette wrote: > It's been fairly quiet on this thread for this release for some reason. I > assume that can only mean that this is to be the

Re: Code Freeze 3.2.3/3.1.5

Push a commit to master earlier today to fix that issue we talked about last week regarding the failing TraversalInterruptionTest. Travis has been happy and I can't seem to get it to fail locally. I think it's in good shape. If you were having problems with that before, please give it a try now.

Code Freeze 3.2.3/3.1.5

We're supposed to start code freeze tomorrow, but we are a little behind. Still have one PR left to merge and it needs a rebase: https://github.com/apache/tinkerpop/pull/448 So expect that to get merged for 3.2.3 during code freeze week, but nothing in that PR should preclude providers from