Re: [DISCUSS] Gremlin JavaScript release

I really think that we need to get as many of the GLV test issues resolved as possible before the release. I'm not so sure we've even created issues for all the failures at this point. Some problems haven't even been classified yet to create a proper issue. I'm going to try to spend some time on th

Re: [DISCUSS] Gremlin JavaScript release

First week of April sounds good to me. On Fri, Feb 23, 2018 at 12:34 PM, Stephen Mallette wrote: > Ok - i was just asking for clarity because this thread started as a > discussion on a "beta" release. > > Our last release was in december, so I suppose it would be time to get > another one out. I

Re: [DISCUSS] Gremlin JavaScript release

Ok - i was just asking for clarity because this thread started as a discussion on a "beta" release. Our last release was in december, so I suppose it would be time to get another one out. I do have a number of issues I'd like to complete for these versions - can we tentatively say that we release

Re: [DISCUSS] Gremlin JavaScript release

I'm referring to an official release of all artifacts for versions 3.2.8 and 3.3.2. The JavaScript GLV has been reviewed and merged, the test suite is in good shape. This GLV has been in the pipeline for a long time now, I think we should make the last effort for it to be generally available. BTW,

Re: [DISCUSS] Gremlin JavaScript release

You're referring to a gremlin-javascript release candidate and not to a general official release of all artifacts (java, .net, etc) for 3.3.2/3.2.8), right? On Wed, Feb 21, 2018 at 9:57 AM, Jorge Bay Gondra wrote: > Hi, > Regarding the npm issue, we created a ticket on the npm issue tracker: > h

Re: [DISCUSS] Gremlin JavaScript release

Hi, Regarding the npm issue, we created a ticket on the npm issue tracker: https://github.com/npm/registry/issues/281 and contacted support. We are waiting for a response from them, but in any case if it takes to long for npm support to look at it, Jean-Baptiste could grant the individual members

Re: [DISCUSS] Gremlin JavaScript release

Any luck? On Wed, Feb 14, 2018 at 9:43 AM, Jorge Bay Gondra wrote: > hm... that's weird... It's working on my end with a different package... > > Maybe use a newer npm cli version? > > If npm access is still failing after cli upgrade, you could use npm owner >

Re: [DISCUSS] Gremlin JavaScript release

hm... that's weird... It's working on my end with a different package... Maybe use a newer npm cli version? If npm access is still failing after cli upgrade, you could use npm owner to add any other tinkerpop member

Re: [DISCUSS] Gremlin JavaScript release

Getting a 403 Forbidden error: $ npm access grant read-write tinkerpop:developers gremlin npm http request PUT https://registry.npmjs.org/-/team/tinkerpop/developers/package npm http 403 https://registry.npmjs.org/-/team/tinkerpop/developers/package npm ERR! code E403 npm ERR! Forbidden : -/team/t

Re: [DISCUSS] Gremlin JavaScript release

gremlin-javascript is not org scoped but "tinkerpop:developers" has write access to it: npm access ls-packages tinkerpop:developers What's the response for: npm access grant read-write tinkerpop:developers gremlin On Tue, Feb 13, 2018 at 3:42 PM, Jean-Baptiste Musso wrote: > Hmm. It looks

Re: [DISCUSS] Gremlin JavaScript release

Hmm. It looks like you can only grant access to team of developers for @scoped package, but not for standard (unscoped) packages. I can make the "tinkerpop" user owner of that "gremlin" package, if that helps. Jean-Baptiste On Tue, Feb 13, 2018 at 9:58 AM, Jorge Bay Gondra wrote: > Jean-Baptist

Re: [DISCUSS] Gremlin JavaScript release

I'm reasonably concerned about TINKERPOP-1857 - the number of test failures and the character of the failures for javascript seem to indicate to me that there is something inherently wrong with gremlin-javascript operations. I think that we should investigate and solve the core problems there befor

Re: [DISCUSS] Gremlin JavaScript release

Jean-Baptiste, could you grant tinkerpop:developers team access to the gremlin package? Once we all have access, it would be nice to have a beta release of 3.2.8/3.3.2 as soon as possible, to allow users to start giving it a try. There aren't any others tickets in JIRA affecting the javascript GL

Re: [DISCUSS] Gremlin JavaScript release

I've added The Baptist to the the org in npm - all done On Mon, Feb 5, 2018 at 12:20 PM, Stephen Mallette wrote: > I have no objections to using "gremlin" since it sounds like we have ways > to make sure users don't break in unclear ways. I'll give others a chance > to respond and barring no add

Re: [DISCUSS] Gremlin JavaScript release

I have no objections to using "gremlin" since it sounds like we have ways to make sure users don't break in unclear ways. I'll give others a chance to respond and barring no additional discussion will get The Baptist added to the org in npm. i guess we can proceed to the next step from there. On M

Re: [DISCUSS] Gremlin JavaScript release

Reusing the existing package name while adding a deprecation message, sounds good to me then. Keep in mind we will be releasing both for 3.2.x and 3.3.x branches, so any deprecation message should be for versions lower than 3.2. If all agree, the next step will be to add jbmusso to tinkerpop org

Re: [DISCUSS] Gremlin JavaScript release

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

Re: [DISCUSS] Gremlin JavaScript release

It stinks that we would break 3K+ downloads. I don't know the npm environment too well. Can a break be expected for people? The current version of https://www.npmjs.com/package/gremlin is at 2.6.0 and we would publish at 3.x which people could expect as a breaking change, no? On Tue, Jan 30, 2018

[DISCUSS] Gremlin JavaScript release

Hi, Now that the JavaScript GLV has been merged, it will be nice to have an official pre-release (RC / beta) on the npm package manager as soon as possible to allow users to start giving it a try. The package name identifier in the package.json is currently gremlin-javascript