[
https://issues.apache.org/jira/browse/TINKERPOP-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752138#comment-16752138
]
Jean-Baptiste Musso commented on TINKERPOP-2137:
This could require different build
> Boyz II Men - ha, I hadn't considered that angle. I assumed the 4 Seasons
> was a Vivaldi reference.
Haha, me neither! I actually didn't know this group. That was indeed a
Vivaldi reference.
Jean-Baptiste
On Thu, Mar 1, 2018 at 2:33 PM, Jason Plurad wrote:
> Boyz II Men -
The 4 Seasons of Gremlin.
Also ok for TinkerPop 4. Works for 3.4.x series though!
Jean-Baptiste
On Tue, Feb 27, 2018 at 3:47 PM, Stephen Mallette
wrote:
> We need a release name and associated Gremlin logo for the 3.4.x series of
> TinkerPop. Recall that names should be
; users don't end up with some image that isn't actively maintained.
> >>>>>
> >>>>> Another advantage of integrating the images in TinkerPop would
> >> probably
> >>>>> be that the deployment could be integrated into TinkerPop's usual
> deprecation message should be for versions lower than 3.2.
> > >>
> > >> If all agree, the next step will be to add jbmusso to tinkerpop org on
> > npm
> > >> and add him to the "developers" team. I can't do it, as I'm not an
> > &quo
npm (and yarn) now freeze versions aggressively in package.json and
package-lock.json or yarn.lock, respectively. Publishing a new version on
the v3.y.z (v.3.3.2) shouldn't be a concern for most users since, luckily,
I never published past the 2.y.z major version on npm.
What I'm thinking is that
d on the same version number.
> Ideally the first release of gremlin-javascript should go into play for
> 3.3.2/3.2.8.
>
> On Fri, Dec 1, 2017 at 5:09 AM, Jean-Baptiste Musso <jbmu...@gmail.com>
> wrote:
>
> > Hi TinkerPop,
> >
> > With the recent w
Hi TinkerPop,
With the recent work on gremlin-javascript by Jorge [1], I see no reason
for the "gremlin" package currently published on npmjs.org [2] to continue
to exist as a distinct project. Newcomers would be so confused, and I don't
think fragmentation is a good idea here. I think it should
Dear TinkerPop,
I published a couple automatically built Docker images for gremlin-server
and gremlin-console (current image tags: latest, 3.2.4, 3.2 and 3):
https://hub.docker.com/r/jbmusso/gremlin-server/
https://hub.docker.com/r/jbmusso/gremlin-console/
I built these because I needed to
[
https://issues.apache.org/jira/browse/TINKERPOP-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15990763#comment-15990763
]
Jean-Baptiste Musso commented on TINKERPOP-1672:
Heh, yup - I kind of opened
Jean-Baptiste Musso created TINKERPOP-1672:
--
Summary: Use python-style syntax for YAML configuration files
Key: TINKERPOP-1672
URL: https://issues.apache.org/jira/browse/TINKERPOP-1672
Cheers Robert!
Jean-Baptiste
On Tue, Apr 18, 2017 at 5:16 PM, Stephen Mallette
wrote:
> We would like to announce that Robert Dale is now a member of the Apache
> TinkerPop PMC. Robert has been a helpful to the TinkerPop community in a
> variety of ways for some time now
Interesting thing. +1 to adding HGraphDB to the list.
Minor concern: I'm not sure if we want to manage a curated list of
implementations and maybe restrict to more mature projects. I'm just
thinking out loud here: I'm not targeting HGraphDB specifically (and I wish
them good luck - *cheers*). My
Welcome aboard Robert!
On Thursday, 27 October 2016, Stephen Mallette wrote:
> The Project Management Committee (PMC) for Apache TinkerPop has asked
> Robert Dale to become a committer and we are pleased to announce that he
> has accepted.
>
> Robert has submitted a number
re() best as well.
>
> On Wed, Sep 21, 2016 at 11:46 AM, Jean-Baptiste Musso <jbmu...@gmail.com
> <javascript:;>>
> wrote:
>
> > I think barrier().store() for .aggregate() is very appropriate and fully
> > tells what is going on.
> >
> > I
github.com/tinkerpop/blueprints/wiki/Batch-Implementation
>
> Thanks!
> -- Jason
> On Mon, Jul 11, 2016 at 6:36 PM Jean-Baptiste Musso <jbmu...@gmail.com>
> wrote:
>
>> Quick follow up - the changes to the TP2 Gremlin documentation are now
>> live. Props to Dylan since I could
Dear devs,
I was thinking recently that we could add a deprecation warning
message on top of all former Github Wiki pages and warn visitors that
a new version of TinkerPop is available. I think this was also brought
up recently on the mailing list so I'm opening a discussion here.
I feel that
I think this is a good idea. This could make these releases look more
"stable": I've often felt that the -incubating suffix somehow made
releases look "alpha-ish" / "beta-ish", even though they were not.
Naming aside, bug fixes never hurt.
Jean-Baptiste
On Wed, May 25, 2016 at 12:49 AM, Stephen
18 matches
Mail list logo