Re: Code Freeze 3.1.4/3.2.2

2016-09-12 Thread Stephen Mallette
yeah - those are present. But there upgrade documentation doesn't mention it - we should have had a nice write up there: http://tinkerpop.apache.org/docs/3.2.2/upgrade/#_tinkerpop_3_2_2 On Mon, Sep 12, 2016 at 10:56 AM, Marko Rodriguez wrote: > Hi, > > In TINKERPOP-1278,

Re: Code Freeze 3.1.4/3.2.2

2016-09-12 Thread Marko Rodriguez
Hi, In TINKERPOP-1278, the notes about Gremlin-Python were added. Perhaps a bad merge? Just checked TINKERPOP-1278 and the notes are still there: [[release-3-2-2]] TinkerPop 3.2.2 (NOT OFFICIALLY RELEASED YET) ~ * Added `gremlin-python` package as a

Re: Code Freeze 3.1.4/3.2.2

2016-09-12 Thread Stephen Mallette
wow - 3.2.2 was really messy for some reason - just noticed that upgrade docs don't mention gremlin-python at all...how did that get by?! On Mon, Sep 12, 2016 at 6:24 AM, Stephen Mallette wrote: > totally flubbed the first release to pypi. i realized that i

Re: Code Freeze 3.1.4/3.2.2

2016-09-12 Thread Stephen Mallette
totally flubbed the first release to pypi. i realized that i didn't have license/notice in the pypi distributions after i deployed 3.2.2. i decided to add them, delete the old distribution and then re-upload. i didn't realize that deleting the release from pypi deletes the files but the name,

Re: Code Freeze 3.1.4/3.2.2

2016-09-06 Thread Stephen Mallette
Oh - a quick note to those voting who use validate-distribution.sh. Ted just added his gpg stuff to the KEYS file: https://dist.apache.org/repos/dist/dev/tinkerpop/KEYS You will need to import his key with: $ gpg --import KEYS if you don't validate-distribution.sh won't be happy and you will

Re: Code Freeze 3.1.4/3.2.2

2016-09-06 Thread Stephen Mallette
Looks like the plan to split the release manager duties between 3.1.4/3.2.2 was a success. It required very little communication aside from a few messages in HipChat. I actually found it easier to do this way because I felt focused on just the release i was working on - in the drudgery of release

Re: Code Freeze 3.1.4/3.2.2

2016-09-06 Thread Stephen Mallette
I've started working on release stuff, though it occurred to me that I'm dependent on Ted completing certain aspects of his 3.1.4 release so that tp31 can merge to master with all the "release" updates. Anyway, I'll go as far as I can then wait for word from Ted on 3.1.4. On Fri, Sep 2, 2016 at

Re: Code Freeze 3.1.4/3.2.2

2016-09-02 Thread Stephen Mallette
Ted, fixed up some javadoc on tp31 branch - meant to do it earlier in the week (but forgot unfortunately): https://issues.apache.org/jira/browse/TINKERPOP-1418 Updated CHANGELOG with the JIRA issue. Anyway, everything is looking pretty good for release next week. On Thu, Sep 1, 2016 at 6:21 PM,

Re: Code Freeze 3.1.4/3.2.2

2016-09-01 Thread Ted Wilmes
Cool, thanks for the update. I had not merged tp31 back into master after my changelog updates so thanks for taking care of that. --Ted On Thu, Sep 1, 2016 at 12:54 PM, Stephen Mallette wrote: > Ted, I noticed some formatting problems in the headers for asciidoc on the >

Re: Code Freeze 3.1.4/3.2.2

2016-09-01 Thread Stephen Mallette
Ted, I noticed some formatting problems in the headers for asciidoc on the tp31 branch. I corrected those. I don't think you need to republish the SNAPSHOT docs over that minor change. Obviously, we'd get the fixes in the official release. I also implemented this on tp31:

Re: Code Freeze 3.1.4/3.2.2

2016-08-31 Thread Ted Wilmes
The 3.1.4-SNAPSHOT docs have been published to: http://tinkerpop.apache. org/docs/3.1.4-SNAPSHOT/ Changelog bugs and improvements have also been updated with where we stand at this point with 3.1.4: https://github.com/apache/tinkerpop/blob/tp31/CHANGELOG.asciidoc Thanks, Ted On Sun, Aug 28,

Code Freeze 3.1.4/3.2.2

2016-08-27 Thread Stephen Mallette
Code freeze begins today. Some minor changes to expect on master: + We have one lingering PR that needs to be merged once it is rebased: https://github.com/apache/tinkerpop/pull/385 + I suspect we will see more tests on gremlin-python as well as tweaks to the build process + We may see one more