[INFO] Jira notification email update

[Hadrian Zbarcea]

Hi,

I had a quick chat with infra@ today and they updated the notification 
email address to be this one. Before it was sending to the old incubator 
dev email.


Just so you know in case you need to update your mail filters.

Cheers,
Hadrian

Re: Request for graphic usage permission (Gremlin-Illustrations)

[Hadrian Zbarcea]

Second. +1

Hadrian

On 08/19/2016 12:56 PM, Marko Rodriguez wrote:

Hello,

I believe that this is an acceptable use of our graphics. If no one disagrees, 
then Thomas, please feel free to use the graphics as you specified starting 
Monday morning (3-day lazy consensus).

Thank you for your request,
Marko.

http://markorodriguez.com




On Aug 19, 2016, at 6:55 AM, Thomas Efer  wrote:

Dear Apache TinkerPop community,

my name is Thomas Efer and I am a researcher in the field of Natural
Language Processing at the University of Leipzig, Germany. A while ago, (in
the pre-Apache days of TinkerPop) I wrote an internal research prototype /
educational tool for graph data analysis ("Gremlin's Property Graph Lab")
in which I included two of the Gremlin illustrations. The software is not
public (and probably never will be, mainly for the lack of time to fix
REPL-related security issues - and eventually there will be newer and
better tools for teaching property graph & traversal basics anyway, like
Gremlin-Bin...)

With this message I would like to ask for your permission to reproduce a
screenshot of said program within my dissertation thesis about "Graph
Databases for Text Representation in the e-Humanities" (German language).
The document will be available free of charge and I would include the
needed copyright information for the image, in a way that does not suggest
any endorsement of Apache Tinkerpop.

The images in question are:
https://svn.apache.org/repos/asf/tinkerpop/site/docs/3.0.0-i
ncubating/images/gremlin-running.png (non-dressed-up)
https://svn.apache.org/repos/asf/tinkerpop/site/docs/3.0.0-i
ncubating/images/gremlin-lab-coat.png (whole character scene)

Thank you for considering my request! Please let me know if you need more
details.

Best Regards


Thomas Efer

--

Thomas Efer M.Sc
Abteilung Automatische Sprachverarbeitung
Institut für Informatik | Universität Leipzig
Augustusplatz 10 | 04109 Leipzig
phone: 0049 - 341 - 97 - 32298
fax:   0049 - 341 - 97 - 32299
mail: e...@informatik.uni-leipzig.de

Re: [VOTE] TinkerPop 3.2.1 Release

[Hadrian Zbarcea]

+1

Stephen, a -1 on a release is not a veto, see the "votes on package 
releases" section on the foundation site [1]. It is up to the release 
manager to decide how to proceed. Usually releases are redone not 
because of the -1, but because there is a valid reason behind the -1. 
Experienced committers and contributors understand if a -1 is warranted 
and weird -1s are rare. It is also my preference (and that's what I did 
in the past) to cancel releases even based on non-binding -1s, because 
the voice of contributors matters too.


Pretty cool that dialogue led to consensus and actions on how to make 
progress. Another proof of how awesome the Tinkerpop community is.


Cheers,
Hadrian

On 07/20/2016 12:01 PM, Stephen Mallette wrote:

Pieter, Thanks as usual for testing. I would offer than this is not a case
for a -1. Note that a -1 says we abort the release completely.

imo, a -1 should be reserved for when there is a massive bug that brings
down the house - meaning the system is abend in some way and there are no
workarounds. a -1 might also be presented if the packaging is bad somehow -
like we didn't include the documentation in the zips. i could also see a -1
if somehow a GPL'd dependency snuck into our packaging somehow or we
otherwise violated Apache licensing. If other's don't agree, I hope they'll
say so.

in this case, you have a single backend for Sqlg that is failing a single
test that you can temporarily OptOut of for your tests to pass. Users don't
specifically have a workaround for this problem if they use Sqlg and
HSQLDB, but it's less of a "bug" and more of a feature that they can't use
(i.e. they can't interrupt a running traversal). To me, I don't think we
need to stop release of TinkerPop over that narrow case.

Would you reconsider your -1 based on that logic?



On Wed, Jul 20, 2016 at 11:45 AM, pieter-gmail 
wrote:


Hi,

Ran all Sqlg's tests and the process and structured  test suites.
But alas there are failures.

TraversalInterruptionTest are failing on HSQLDB as the
Thread.interrupt() is intercepted by them and the interrupt flag is reset.
The TraversalInterruptionTest tests themselves suffers from this as its
own Thread.sleep() logic resets the interrupt flag and requires special
resetting. I'd say the current interrupt strategy needs rethinking.

TailTest.g_V_repeatXbothX_timesX3X_tailX7X fails. I added a few more,
repeat followed by a tail step, tests in sqlg, all of which also fails.
Jason has already proposed a fix for this here
.

vote -1

Thanks
Pieter



On 19/07/2016 15:20, Stephen Mallette wrote:

Hello,

We are happy to announce that TinkerPop 3.2.1 is ready for release - note
the lack of "-incubating" everywhere.  :)

The release artifacts can be found at this location:
https://dist.apache.org/repos/dist/dev/tinkerpop/3.2.1/

The source distribution is provided by:
apache-tinkerpop-3.2.1-src.zip

Two binary distributions are provided for user convenience:
apache-gremlin-console-3.2.1-bin.zip
apache-gremlin-server-3.2.1-bin.zip

The GPG key used to sign the release artifacts is available at:
 https://dist.apache.org/repos/dist/dev/tinkerpop/KEYS

The online docs can be found here:
http://tinkerpop.apache.org/docs/3.2.1/reference/ (user docs)
http://tinkerpop.apache.org/docs/3.2.1/upgrade/ (upgrade docs)
http://tinkerpop.apache.org/javadocs/3.2.1/core/ (core javadoc)
http://tinkerpop.apache.org/javadocs/3.2.1/full/ (full javadoc)

The tag in Apache Git can be found here:



https://git-wip-us.apache.org/repos/asf?p=tinkerpop.git;a=tag;h=c5a9e2815e76f044e6b33b773b6bb0bb048270cc


The release notes are available here:


https://github.com/apache/tinkerpop/blob/3.2.1/CHANGELOG.asciidoc#release-3-2-1


The [VOTE] will be open for the next 72 hours --- closing Friday (July

22,

2016) at 9:30 am EST.

My vote is +1.

Thank you very much,
Stephen

Re: [DISCUSS] 3.1.x code line

[Hadrian Zbarcea]

+1. It does to me.
Hadrian

On 07/13/2016 04:29 PM, Stephen Mallette wrote:

Since we don't really follow semantic versioning for releases, I thought we
should discuss the 3.1.x code line. We've been steadily adding features
right up to our current 3.1.3 release which we will vote on shortly. I
think it's pretty awesome that we've managed to maintain that older line of
code for as long as we have and I think we've evolved it in a very sensible
way.

I think we should continue to maintain 3.1.x after the 3.1.3 release, which
would mean a 3.1.4 release at some point, but we should strictly limit the
changes there to bug fixes and not do any "new features" on that line of
code (i.e the tp31 branch). As it stands, I don't see any open "bugs" for
the 3.1.3 in JIRA so as of right now, we wouldn't have much planned for
3.1.4.

Does that make sense for everyone?

Re: tinkerpop.com redirect?

[Hadrian Zbarcea]

Done [1]. Thx.

Hadrian

[1] https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-12145

On 06/20/2016 11:40 AM, David Nalley wrote:

File an infra Jira ticket.

https://infrahelp.apache.org


On Mon, Jun 20, 2016 at 9:46 AM, Marko Rodriguez  wrote:

Hi,

How can we make tinkerpop.com redirect to tinkerpop.apache.org instead of 
tinkerpop.incubator.apache.org?

Thanks,
Marko.

http://markorodriguez.com

Re: [DISCUSS] How to Contribute docs

[Hadrian Zbarcea]

Excellent work Stephen!

Hadrian

On 06/07/2016 05:28 PM, Stephen Mallette wrote:

We had some documentation on "how to contribute" but they were kinda weak.
I re-wrote it using the very good "how to contribute" docs from Spark as a
guide. I was kinda annoyed because their stuff was so good, it was hard not
to blatantly just copy some of their points. :)

Anyway, I think it is a good improvement over what we had before. Note that
there are three key sections that I added:

http://tinkerpop.apache.org/docs/3.2.1-SNAPSHOT/dev/developer/#_ways_to_contribute
http://tinkerpop.apache.org/docs/3.2.1-SNAPSHOT/dev/developer/#_considering_code_changes
http://tinkerpop.apache.org/docs/3.2.1-SNAPSHOT/dev/developer/#_contributing_code_changes

Please have a look and let me know if we can be happy with this for
inclusion with 3.2.1/3.1.3 docs.

Re: When does incubator-suffix get dropped?

[Hadrian Zbarcea]

As soon as the graduation is announced.

Homepage, mailing lists done (old ones will forward for a while). Next 
release should drop the 'incubating' part.


Hadrian

On 06/04/2016 02:33 PM, Marko Rodriguez wrote:

Hi,

I’ve been hearing big talky talky that Incubator suffixes are “just handled” — 
Git, homepage, mailing lists. When does talky talky become doey doey?

Thanks,
Marko.

http://markorodriguez.com