The tp32 branch is now re-opened for development. everything has been merged down to master so we're all set for the next round of development. we will announce the 3.1.5 and 3.2.3 releases as soon as the mirrors sync. Ted, we can coordinate that tomorrow.
Thanks to everyone who was able to vote. That was pretty smooth sailing. On Thu, Oct 20, 2016 at 3:02 PM, Ted Wilmes <twil...@gmail.com> wrote: > Hello, > 3.1 has been bumped to 3.1.6-SNAPSHOT and is officially unfrozen. > > Thanks, > Ted > > On Wed, Oct 19, 2016 at 4:01 PM, Stephen Mallette <spmalle...@gmail.com> > wrote: > > > just pushed the tp32 branch. master is now open for 3.3.x work - let's > look > > to leave tp31/tp32 alone until vote is done tomorrow. > > > > note that on master, i added gremlin-tools module and pushed > > gremlin-benchmark under there. gremlin-coverage is in place too so we now > > have a unified coverage report over most of our modules (didn't cover > > hadoop/spark/giraph yet because of dependency issues that need to be > > sovled). > > > > recall that now that we have all this branch complexity, there will > likely > > be a need for multiple pull requests if you make changes on the tp31/tp32 > > lines. Please review the "Pull Requests" section of the docs for more > > information: > > > > http://tinkerpop.apache.org/docs/3.2.3/dev/developer/#pull-requests > > > > > > > > On Tue, Oct 18, 2016 at 6:50 AM, Stephen Mallette <spmalle...@gmail.com> > > wrote: > > > > > 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 have open issues on that line of code, please have a look at them > to > > > see if they should be either descheduled completely or simply moved > > forward > > > to 3.3.0. > > > > > > On Mon, Oct 17, 2016 at 11:40 PM, Daniel Kuppitz <m...@gremlin.guru> > > wrote: > > > > > >> 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 ${DIR_NAME} > > >> echo -n "* building project ... " > > >> LOG_FILE="${TMP_DIR}/mvn-clean-install-${VERSION}.log" > > >> -mvn clean install -q 2>&1 > "${LOG_FILE}" || { > > >> *+mvn clean install -q > "${LOG_FILE}" 2>&1 || {* > > >> echo "failed" > > >> echo > > >> tail -n50 "${LOG_FILE}" > > >> - echo -e "\n\e[1mThe full log file can be inspected under > > >> `pwd`/${LOG_FILE}.\e[0m\n" > > >> *+ echo -e "\n\e[1mThe full log file can be inspected under > > >> ${LOG_FILE}.\e[0m\n"* > > >> exit 1 > > >> } > > >> echo "OK" > > >> > > >> > > >> Cheers, > > >> Daniel > > >> > > >> > > >> On Mon, Oct 17, 2016 at 11:24 PM, Stephen Mallette < > > spmalle...@gmail.com> > > >> wrote: > > >> > > >> > 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 bit of output as it ultimately ends with "OK". > > >> > > > >> > Kuppitz, if you have the fix, maybe post it as a gist here on this > > >> thread. > > >> > Once we re-open master for development you can push the change to > the > > >> repo. > > >> > > > >> > On Mon, Oct 17, 2016 at 2:06 PM, Stephen Mallette < > > spmalle...@gmail.com > > >> > > > >> > wrote: > > >> > > > >> > > 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 <twil...@gmail.com> > > >> 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 > > >> finished > > >> > up > > >> > >> tomorrow. > > >> > >> > > >> > >> --Ted > > >> > >> > > >> > >> On Sun, Oct 16, 2016 at 3:36 PM, Stephen Mallette < > > >> spmalle...@gmail.com > > >> > > > > >> > >> wrote: > > >> > >> > > >> > >> > dahhhh > > >> > >> > > > >> > >> > 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, Robert Dale < > robd...@gmail.com > > > > > >> > >> wrote: > > >> > >> > > > >> > >> > > I think TINKERPOP-1511 > > >> > >> > > <https://issues.apache.org/jira/browse/TINKERPOP-1511> > should > > be > > >> > >> fixed > > >> > >> > in > > >> > >> > > 3.2.3. > > >> > >> > > > > >> > >> > > On Fri, Oct 14, 2016 at 10:09 PM, Ted Wilmes < > > twil...@gmail.com> > > >> > >> wrote: > > >> > >> > > > > >> > >> > > > A fresh 3.1.5-SNAPSHOT has been deployed along with the > docs. > > >> > >> > > > > > >> > >> > > > --Ted > > >> > >> > > > > > >> > >> > > > > > >> > >> > > > > > >> > >> > > > On Fri, Oct 14, 2016 at 2:10 PM, pieter-gmail < > > >> > >> pieter.mar...@gmail.com > > >> > >> > > > > >> > >> > > > wrote: > > >> > >> > > > > > >> > >> > > > > 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 3.2.3-SNAPSHOT again to > > Apache > > >> > >> > Snapshots > > >> > >> > > > > > Repository and also republished the docs: > > >> > >> > > > > > > > >> > >> > > > > > http://tinkerpop.apache.org/docs/3.2.3-SNAPSHOT/ > > >> > >> > > > > > > > >> > >> > > > > > and they look pretty good (there was a problem with > > upgrade > > >> > doc > > >> > >> > > > > > formatting). Upgrade docs look really solid for this > > >> release. > > >> > >> > > > Hopefully, > > >> > >> > > > > > master is fully stable now and we won't need any more > > >> changes > > >> > >> > before > > >> > >> > > I > > >> > >> > > > > > build up the release for vote on monday. > > >> > >> > > > > > > > >> > >> > > > > > > > >> > >> > > > > > On Tue, Oct 11, 2016 at 7:20 PM, Ted Wilmes < > > >> > twil...@gmail.com> > > >> > >> > > wrote: > > >> > >> > > > > > > > >> > >> > > > > >> I was getting failures earlier today off of master. > > Just > > >> > did a > > >> > >> > pull > > >> > >> > > > and > > >> > >> > > > > >> things are looking good. > > >> > >> > > > > >> > > >> > >> > > > > >> --Ted > > >> > >> > > > > >> > > >> > >> > > > > >> On Tue, Oct 11, 2016 at 5:48 PM, Stephen Mallette < > > >> > >> > > > spmalle...@gmail.com > > >> > >> > > > > > > > >> > >> > > > > >> wrote: > > >> > >> > > > > >> > > >> > >> > > > > >>> 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. Marko is still planning to some work to fix up > > >> > >> PeerPressure > > >> > >> > > test > > >> > >> > > > > >>> (can't say I've have trouble with that one myself). > > >> > >> > > > > >>> > > >> > >> > > > > >>> Also, I published a 3.2.3 -SNAPSHOT earlier today btw > > to > > >> the > > >> > >> > Apache > > >> > >> > > > > >>> snapshot repository for testing. > > >> > >> > > > > >>> > > >> > >> > > > > >>> On Fri, Oct 7, 2016 at 6:44 PM, Stephen Mallette < > > >> > >> > > > spmalle...@gmail.com > > >> > >> > > > > > > > >> > >> > > > > >>> wrote: > > >> > >> > > > > >>> > > >> > >> > > > > >>>> 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 > > >> testing > > >> > >> their > > >> > >> > > > > >>>> implementations. Other than that, I think > everything > > >> else > > >> > of > > >> > >> > > > > substance > > >> > >> > > > > >>> is > > >> > >> > > > > >>>> in. > > >> > >> > > > > >>>> > > >> > >> > > > > >>>> I do have one worry about that TraversalInterruption > > >> test > > >> > >> that > > >> > >> > has > > >> > >> > > > > been > > >> > >> > > > > >>>> failing randomly since the LazyBarrierStrategy stuff > > >> went > > >> > in > > >> > >> (i > > >> > >> > > > > think). > > >> > >> > > > > >>>> Marko also mentioned the PeerPressure test. We'll > put > > >> some > > >> > >> elbow > > >> > >> > > > > grease > > >> > >> > > > > >>>> into that next week and try to get those figured out > > and > > >> > more > > >> > >> > > > stable. > > >> > >> > > > > >>>> > > >> > >> > > > > >>>> As a reminder Ted will be release manager for 3.1.5 > > and > > >> > I'll > > >> > >> be > > >> > >> > > > doing > > >> > >> > > > > >>>> 3.2.3. As usual, we will use this thread to > coordinate > > >> > during > > >> > >> > code > > >> > >> > > > > >> freeze > > >> > >> > > > > >>>> week. Please bring up relevant issues here. > > >> > >> > > > > >>>> > > >> > >> > > > > >>>> Thanks, > > >> > >> > > > > >>>> > > >> > >> > > > > >>>> Stephen > > >> > >> > > > > >>>> > > >> > >> > > > > > > >> > >> > > > > > > >> > >> > > > > > >> > >> > > > > >> > >> > > > > >> > >> > > > > >> > >> > > -- > > >> > >> > > Robert Dale > > >> > >> > > > > >> > >> > > > >> > >> > > >> > > > > >> > > > > >> > > > >> > > > > > > > > >
