You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by Jorge Bay Gondra <jo...@gmail.com> on 2018/06/22 13:50:05 UTC
[Discuss] 3.4.0 GLV packages
Hi,
It would be nice to have public alpha/beta releases of the 3.4 GLVs to
start trying out the 3.4 branch.
If needed, I could take the work of publishing the node.js package for this
prerelease.
wdyt?
Jorge
Re: [Discuss] 3.4.0 GLV packages
Posted by Florian Hockmann <fh...@florian-hockmann.de>.
OK, good to now. I thought that GLV packages would also include the
template but I guess that a release candidate for the template wouldn't
make much sense for version 3.4.0 right now anyway. So we can better
publish a rc of the template for 3.2.10 or 3.3.4 at any time.
Am 02.07.2018 um 15:34 schrieb Jorge Bay Gondra:
> I've pushed manually
>
> El lun., 2 jul. 2018 a las 15:07, <fh...@florian-hockmann.de> escribió:
>
>> Shouldn't that also have published a RC version of the new .NET template
>> or did you publish Gremlin.Net manually without using Maven?
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Jorge Bay Gondra <jo...@gmail.com>
>> Gesendet: Montag, 2. Juli 2018 13:49
>> An: dev@tinkerpop.apache.org
>> Betreff: Re: [Discuss] 3.4.0 GLV packages
>>
>> Thanks Stephen!
>>
>> I've published 3.4.0-rc1 on nuget.org:
>> https://www.nuget.org/packages/Gremlin.Net/3.4.0-rc1
>>
>> It's ok to maintain RC for historical reasons :)
>>
>> El lun., 2 jul. 2018 a las 13:10, Stephen Mallette (<spmallette@gmail.com
>>> )
>> escribió:
>>
>>> Since you have access to the node repo, I see no reason not to give
>>> you access to the nuget one as well - invitation sent.
>>>
>>>> For next time, shouldn't we use "alpha/beta" instead of "rc"? rc
>>> denotes code
>>> completion, no further API changes.
>>>
>>> I think we've taken a fairly loose meaning of "release candidate" here
>>> in TinkerPop over the years. Given that we've done so many "release
>> candidate"
>>> releases at this point, I'd say we just stick with the "rc" concept
>>> rather than try to introduce something new now, but if folks think
>>> it's creating confusion somehow, I guess I don't mind changing next
>>> time.
>>>
>>>
>>>
>>> On Mon, Jul 2, 2018 at 6:56 AM Jorge Bay Gondra
>>> <jo...@gmail.com>
>>> wrote:
>>>
>>>> I've published 3.4.0-rc1 on npm:
>>>> https://www.npmjs.com/package/gremlin?activeTab=versions
>>>>
>>>> I don't have access to publish Gremlin.Net on nuget.org, can anyone
>>> grant
>>>> me access?
>>>>
>>>> El lun., 2 jul. 2018 a las 11:45, Jorge Bay Gondra (<
>>>> jorgebaygondra@gmail.com>) escribió:
>>>>
>>>>> About npm, within the "latest" distribution tag
>>>>> <https://docs.npmjs.com/cli/dist-tag>, it sorts by date on their
>>>>> web
>>> UI
>>>>> but the dependencies are resolved correctly according to semver
>>>>> and tilde/caret notations, so there isn't much to worry about
>>>>> except that
>>> the
>>>>> latest shown on the website is not *the* latest :) The most used
>>>>> notation on node.js to note prereleases is x.y.z-beta1 /
>>>> x.y.z-rc1,
>>>>> there is more info here:
>>>>> https://docs.npmjs.com/misc/semver#prerelease-identifiers
>>>>>
>>>>> I'll deploy 3.4.0-rc1 to npm on the "beta" distribution tag, and
>>>> 3.4.0-rc1
>>>>> on nuget.org.
>>>>>
>>>>> For next time, shouldn't we use "alpha/beta" instead of "rc"? rc
>>> denotes
>>>>> code completion, no further API changes.
>>>>>
>>>>> El vie., 29 jun. 2018 a las 21:50, Stephen Mallette (<
>>>> spmallette@gmail.com>)
>>>>> escribió:
>>>>>
>>>>>> For those interested in doing some development/testing against
>>>>>> Python
>>>>>> 3.4.0rc1 is out there on pypi:
>>>>>>
>>>>>> https://pypi.org/project/gremlinpython/3.4.0rc1/
>>>>>>
>>>>>> Jorge, I'll leave the .NET and JS to you. Just to be clear, there
>>>>>> is
>>> no
>>>>>> need to commit anything back to git in terms of this release
>>> candidate.
>>>>>> Just make your edits locally and deploy.
>>>>>>
>>>>>> Also, I'll make an additional quesiton about how NPM
>>>>>> works.....For
>>> .NET
>>>> we
>>>>>> should deploy the version "3.4.0-rc1", but what is the notion of
>>>>>> a "release candidate" in JS terminology? is it also "3.4.0-rc1"
>>>>>> or is it like
>>>> python
>>>>>> with "3.4.0rc1" or something else?
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Jun 29, 2018 at 11:37 AM Stephen Mallette <
>>> spmallette@gmail.com
>>>>>> wrote:
>>>>>>
>>>>>>> yeah - we could have done that earlier in the week. i just
>>>>>>> tagged
>>> the
>>>>>>> current master at 3.4.0-rc1
>>>>>>>
>>>>>>> https://github.com/apache/tinkerpop/tree/3.4.0-rc1
>>>>>>>
>>>>>>> so you can check that tag out and go from there. I can do
>>>>>>> python
>>> later
>>>>>> in
>>>>>>> the day.
>>>>>>>
>>>>>>> By the way, I have a question about npm:
>>>>>>>
>>>>>>> https://www.npmjs.com/package/gremlin
>>>>>>>
>>>>>>> it seems like npm does not sort by the most recent version
>>>>>>> number -
>>> it
>>>>>>> sorts by date deployed (note that the "current" version is
>>> 3.2.9)...is
>>>>>> that
>>>>>>> right? that doesn't affect the "current" version downloaded does
>> it?
>>>> can
>>>>>>> that be changed somehow or do we just need to be careful in how
>>>>>>> we
>>>>>> deploy
>>>>>>> so that our oldest versions go up first?
>>>>>>>
>>>>>>> Lastly, just a reminder to everyone, that this 3.4.0-rc1 is
>>>>>>> just a development release for very early testing purposes. We
>>>>>>> aren't
>>>> promoting
>>>>>>> this convenience release in any way.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Jun 29, 2018 at 11:25 AM Jorge Bay Gondra <
>>>>>>> jorgebaygondra@gmail.com> wrote:
>>>>>>>
>>>>>>>> It looks like there isn't any concerns, can we move forward by
>>>>>> releasing
>>>>>>>> them?
>>>>>>>>
>>>>>>>> I can publish Node.js package and .NET package, if needed. I'm
>>>>>>>> not confident enough to do it for pypi, tho :)
>>>>>>>>
>>>>>>>> El sáb., 23 jun. 2018 a las 12:21, Stephen Mallette (<
>>>>>>>> spmallette@gmail.com>)
>>>>>>>> escribió:
>>>>>>>>
>>>>>>>>> I don't have a problem with doing that. Indeed we have JVM
>>>> snapshots
>>>>>>>>> deployed for 3.4.0 on Apache Snapshots Repo, so it makes
>>>>>>>>> sense to
>>>>>> have
>>>>>>>> dev
>>>>>>>>> artifacts deployed for the testing purposes for GLVs. Let's
>>>>>>>>> wait
>>>> the
>>>>>>>>> standard 72 hours for any concerns and then get some release
>>>>>> candidates
>>>>>>>>> released.
>>>>>>>>>
>>>>>>>>> On Fri, Jun 22, 2018 at 9:50 AM Jorge Bay Gondra <
>>>>>>>> jorgebaygondra@gmail.com
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>> It would be nice to have public alpha/beta releases of the
>>>>>>>>>> 3.4
>>>>>> GLVs to
>>>>>>>>>> start trying out the 3.4 branch.
>>>>>>>>>>
>>>>>>>>>> If needed, I could take the work of publishing the node.js
>>>> package
>>>>>> for
>>>>>>>>> this
>>>>>>>>>> prerelease.
>>>>>>>>>>
>>>>>>>>>> wdyt?
>>>>>>>>>> Jorge
>>>>>>>>>>
>>
Re: [Discuss] 3.4.0 GLV packages
Posted by Jorge Bay Gondra <jo...@gmail.com>.
I've pushed manually
El lun., 2 jul. 2018 a las 15:07, <fh...@florian-hockmann.de> escribió:
> Shouldn't that also have published a RC version of the new .NET template
> or did you publish Gremlin.Net manually without using Maven?
>
> -----Ursprüngliche Nachricht-----
> Von: Jorge Bay Gondra <jo...@gmail.com>
> Gesendet: Montag, 2. Juli 2018 13:49
> An: dev@tinkerpop.apache.org
> Betreff: Re: [Discuss] 3.4.0 GLV packages
>
> Thanks Stephen!
>
> I've published 3.4.0-rc1 on nuget.org:
> https://www.nuget.org/packages/Gremlin.Net/3.4.0-rc1
>
> It's ok to maintain RC for historical reasons :)
>
> El lun., 2 jul. 2018 a las 13:10, Stephen Mallette (<spmallette@gmail.com
> >)
> escribió:
>
> > Since you have access to the node repo, I see no reason not to give
> > you access to the nuget one as well - invitation sent.
> >
> > > For next time, shouldn't we use "alpha/beta" instead of "rc"? rc
> > denotes code
> > completion, no further API changes.
> >
> > I think we've taken a fairly loose meaning of "release candidate" here
> > in TinkerPop over the years. Given that we've done so many "release
> candidate"
> > releases at this point, I'd say we just stick with the "rc" concept
> > rather than try to introduce something new now, but if folks think
> > it's creating confusion somehow, I guess I don't mind changing next time.
> >
> >
> >
> > On Mon, Jul 2, 2018 at 6:56 AM Jorge Bay Gondra
> > <jo...@gmail.com>
> > wrote:
> >
> > > I've published 3.4.0-rc1 on npm:
> > > https://www.npmjs.com/package/gremlin?activeTab=versions
> > >
> > > I don't have access to publish Gremlin.Net on nuget.org, can anyone
> > grant
> > > me access?
> > >
> > > El lun., 2 jul. 2018 a las 11:45, Jorge Bay Gondra (<
> > > jorgebaygondra@gmail.com>) escribió:
> > >
> > > > About npm, within the "latest" distribution tag
> > > > <https://docs.npmjs.com/cli/dist-tag>, it sorts by date on their
> > > > web
> > UI
> > > > but the dependencies are resolved correctly according to semver
> > > > and tilde/caret notations, so there isn't much to worry about
> > > > except that
> > the
> > > > latest shown on the website is not *the* latest :) The most used
> > > > notation on node.js to note prereleases is x.y.z-beta1 /
> > > x.y.z-rc1,
> > > > there is more info here:
> > > > https://docs.npmjs.com/misc/semver#prerelease-identifiers
> > > >
> > > > I'll deploy 3.4.0-rc1 to npm on the "beta" distribution tag, and
> > > 3.4.0-rc1
> > > > on nuget.org.
> > > >
> > > > For next time, shouldn't we use "alpha/beta" instead of "rc"? rc
> > denotes
> > > > code completion, no further API changes.
> > > >
> > > > El vie., 29 jun. 2018 a las 21:50, Stephen Mallette (<
> > > spmallette@gmail.com>)
> > > > escribió:
> > > >
> > > >> For those interested in doing some development/testing against
> > > >> Python
> > > >> 3.4.0rc1 is out there on pypi:
> > > >>
> > > >> https://pypi.org/project/gremlinpython/3.4.0rc1/
> > > >>
> > > >> Jorge, I'll leave the .NET and JS to you. Just to be clear, there
> > > >> is
> > no
> > > >> need to commit anything back to git in terms of this release
> > candidate.
> > > >> Just make your edits locally and deploy.
> > > >>
> > > >> Also, I'll make an additional quesiton about how NPM
> > > >> works.....For
> > .NET
> > > we
> > > >> should deploy the version "3.4.0-rc1", but what is the notion of
> > > >> a "release candidate" in JS terminology? is it also "3.4.0-rc1"
> > > >> or is it like
> > > python
> > > >> with "3.4.0rc1" or something else?
> > > >>
> > > >>
> > > >>
> > > >> On Fri, Jun 29, 2018 at 11:37 AM Stephen Mallette <
> > spmallette@gmail.com
> > > >
> > > >> wrote:
> > > >>
> > > >> > yeah - we could have done that earlier in the week. i just
> > > >> > tagged
> > the
> > > >> > current master at 3.4.0-rc1
> > > >> >
> > > >> > https://github.com/apache/tinkerpop/tree/3.4.0-rc1
> > > >> >
> > > >> > so you can check that tag out and go from there. I can do
> > > >> > python
> > later
> > > >> in
> > > >> > the day.
> > > >> >
> > > >> > By the way, I have a question about npm:
> > > >> >
> > > >> > https://www.npmjs.com/package/gremlin
> > > >> >
> > > >> > it seems like npm does not sort by the most recent version
> > > >> > number -
> > it
> > > >> > sorts by date deployed (note that the "current" version is
> > 3.2.9)...is
> > > >> that
> > > >> > right? that doesn't affect the "current" version downloaded does
> it?
> > > can
> > > >> > that be changed somehow or do we just need to be careful in how
> > > >> > we
> > > >> deploy
> > > >> > so that our oldest versions go up first?
> > > >> >
> > > >> > Lastly, just a reminder to everyone, that this 3.4.0-rc1 is
> > > >> > just a development release for very early testing purposes. We
> > > >> > aren't
> > > promoting
> > > >> > this convenience release in any way.
> > > >> >
> > > >> >
> > > >> >
> > > >> > On Fri, Jun 29, 2018 at 11:25 AM Jorge Bay Gondra <
> > > >> > jorgebaygondra@gmail.com> wrote:
> > > >> >
> > > >> >> It looks like there isn't any concerns, can we move forward by
> > > >> releasing
> > > >> >> them?
> > > >> >>
> > > >> >> I can publish Node.js package and .NET package, if needed. I'm
> > > >> >> not confident enough to do it for pypi, tho :)
> > > >> >>
> > > >> >> El sáb., 23 jun. 2018 a las 12:21, Stephen Mallette (<
> > > >> >> spmallette@gmail.com>)
> > > >> >> escribió:
> > > >> >>
> > > >> >> > I don't have a problem with doing that. Indeed we have JVM
> > > snapshots
> > > >> >> > deployed for 3.4.0 on Apache Snapshots Repo, so it makes
> > > >> >> > sense to
> > > >> have
> > > >> >> dev
> > > >> >> > artifacts deployed for the testing purposes for GLVs. Let's
> > > >> >> > wait
> > > the
> > > >> >> > standard 72 hours for any concerns and then get some release
> > > >> candidates
> > > >> >> > released.
> > > >> >> >
> > > >> >> > On Fri, Jun 22, 2018 at 9:50 AM Jorge Bay Gondra <
> > > >> >> jorgebaygondra@gmail.com
> > > >> >> > >
> > > >> >> > wrote:
> > > >> >> >
> > > >> >> > > Hi,
> > > >> >> > > It would be nice to have public alpha/beta releases of the
> > > >> >> > > 3.4
> > > >> GLVs to
> > > >> >> > > start trying out the 3.4 branch.
> > > >> >> > >
> > > >> >> > > If needed, I could take the work of publishing the node.js
> > > package
> > > >> for
> > > >> >> > this
> > > >> >> > > prerelease.
> > > >> >> > >
> > > >> >> > > wdyt?
> > > >> >> > > Jorge
> > > >> >> > >
> > > >> >> >
> > > >> >>
> > > >> >
> > > >>
> > > >
> > >
> >
>
>
AW: [Discuss] 3.4.0 GLV packages
Posted by fh...@florian-hockmann.de.
Shouldn't that also have published a RC version of the new .NET template or did you publish Gremlin.Net manually without using Maven?
-----Ursprüngliche Nachricht-----
Von: Jorge Bay Gondra <jo...@gmail.com>
Gesendet: Montag, 2. Juli 2018 13:49
An: dev@tinkerpop.apache.org
Betreff: Re: [Discuss] 3.4.0 GLV packages
Thanks Stephen!
I've published 3.4.0-rc1 on nuget.org:
https://www.nuget.org/packages/Gremlin.Net/3.4.0-rc1
It's ok to maintain RC for historical reasons :)
El lun., 2 jul. 2018 a las 13:10, Stephen Mallette (<sp...@gmail.com>)
escribió:
> Since you have access to the node repo, I see no reason not to give
> you access to the nuget one as well - invitation sent.
>
> > For next time, shouldn't we use "alpha/beta" instead of "rc"? rc
> denotes code
> completion, no further API changes.
>
> I think we've taken a fairly loose meaning of "release candidate" here
> in TinkerPop over the years. Given that we've done so many "release candidate"
> releases at this point, I'd say we just stick with the "rc" concept
> rather than try to introduce something new now, but if folks think
> it's creating confusion somehow, I guess I don't mind changing next time.
>
>
>
> On Mon, Jul 2, 2018 at 6:56 AM Jorge Bay Gondra
> <jo...@gmail.com>
> wrote:
>
> > I've published 3.4.0-rc1 on npm:
> > https://www.npmjs.com/package/gremlin?activeTab=versions
> >
> > I don't have access to publish Gremlin.Net on nuget.org, can anyone
> grant
> > me access?
> >
> > El lun., 2 jul. 2018 a las 11:45, Jorge Bay Gondra (<
> > jorgebaygondra@gmail.com>) escribió:
> >
> > > About npm, within the "latest" distribution tag
> > > <https://docs.npmjs.com/cli/dist-tag>, it sorts by date on their
> > > web
> UI
> > > but the dependencies are resolved correctly according to semver
> > > and tilde/caret notations, so there isn't much to worry about
> > > except that
> the
> > > latest shown on the website is not *the* latest :) The most used
> > > notation on node.js to note prereleases is x.y.z-beta1 /
> > x.y.z-rc1,
> > > there is more info here:
> > > https://docs.npmjs.com/misc/semver#prerelease-identifiers
> > >
> > > I'll deploy 3.4.0-rc1 to npm on the "beta" distribution tag, and
> > 3.4.0-rc1
> > > on nuget.org.
> > >
> > > For next time, shouldn't we use "alpha/beta" instead of "rc"? rc
> denotes
> > > code completion, no further API changes.
> > >
> > > El vie., 29 jun. 2018 a las 21:50, Stephen Mallette (<
> > spmallette@gmail.com>)
> > > escribió:
> > >
> > >> For those interested in doing some development/testing against
> > >> Python
> > >> 3.4.0rc1 is out there on pypi:
> > >>
> > >> https://pypi.org/project/gremlinpython/3.4.0rc1/
> > >>
> > >> Jorge, I'll leave the .NET and JS to you. Just to be clear, there
> > >> is
> no
> > >> need to commit anything back to git in terms of this release
> candidate.
> > >> Just make your edits locally and deploy.
> > >>
> > >> Also, I'll make an additional quesiton about how NPM
> > >> works.....For
> .NET
> > we
> > >> should deploy the version "3.4.0-rc1", but what is the notion of
> > >> a "release candidate" in JS terminology? is it also "3.4.0-rc1"
> > >> or is it like
> > python
> > >> with "3.4.0rc1" or something else?
> > >>
> > >>
> > >>
> > >> On Fri, Jun 29, 2018 at 11:37 AM Stephen Mallette <
> spmallette@gmail.com
> > >
> > >> wrote:
> > >>
> > >> > yeah - we could have done that earlier in the week. i just
> > >> > tagged
> the
> > >> > current master at 3.4.0-rc1
> > >> >
> > >> > https://github.com/apache/tinkerpop/tree/3.4.0-rc1
> > >> >
> > >> > so you can check that tag out and go from there. I can do
> > >> > python
> later
> > >> in
> > >> > the day.
> > >> >
> > >> > By the way, I have a question about npm:
> > >> >
> > >> > https://www.npmjs.com/package/gremlin
> > >> >
> > >> > it seems like npm does not sort by the most recent version
> > >> > number -
> it
> > >> > sorts by date deployed (note that the "current" version is
> 3.2.9)...is
> > >> that
> > >> > right? that doesn't affect the "current" version downloaded does it?
> > can
> > >> > that be changed somehow or do we just need to be careful in how
> > >> > we
> > >> deploy
> > >> > so that our oldest versions go up first?
> > >> >
> > >> > Lastly, just a reminder to everyone, that this 3.4.0-rc1 is
> > >> > just a development release for very early testing purposes. We
> > >> > aren't
> > promoting
> > >> > this convenience release in any way.
> > >> >
> > >> >
> > >> >
> > >> > On Fri, Jun 29, 2018 at 11:25 AM Jorge Bay Gondra <
> > >> > jorgebaygondra@gmail.com> wrote:
> > >> >
> > >> >> It looks like there isn't any concerns, can we move forward by
> > >> releasing
> > >> >> them?
> > >> >>
> > >> >> I can publish Node.js package and .NET package, if needed. I'm
> > >> >> not confident enough to do it for pypi, tho :)
> > >> >>
> > >> >> El sáb., 23 jun. 2018 a las 12:21, Stephen Mallette (<
> > >> >> spmallette@gmail.com>)
> > >> >> escribió:
> > >> >>
> > >> >> > I don't have a problem with doing that. Indeed we have JVM
> > snapshots
> > >> >> > deployed for 3.4.0 on Apache Snapshots Repo, so it makes
> > >> >> > sense to
> > >> have
> > >> >> dev
> > >> >> > artifacts deployed for the testing purposes for GLVs. Let's
> > >> >> > wait
> > the
> > >> >> > standard 72 hours for any concerns and then get some release
> > >> candidates
> > >> >> > released.
> > >> >> >
> > >> >> > On Fri, Jun 22, 2018 at 9:50 AM Jorge Bay Gondra <
> > >> >> jorgebaygondra@gmail.com
> > >> >> > >
> > >> >> > wrote:
> > >> >> >
> > >> >> > > Hi,
> > >> >> > > It would be nice to have public alpha/beta releases of the
> > >> >> > > 3.4
> > >> GLVs to
> > >> >> > > start trying out the 3.4 branch.
> > >> >> > >
> > >> >> > > If needed, I could take the work of publishing the node.js
> > package
> > >> for
> > >> >> > this
> > >> >> > > prerelease.
> > >> >> > >
> > >> >> > > wdyt?
> > >> >> > > Jorge
> > >> >> > >
> > >> >> >
> > >> >>
> > >> >
> > >>
> > >
> >
>
Re: [Discuss] 3.4.0 GLV packages
Posted by Jorge Bay Gondra <jo...@gmail.com>.
Thanks Stephen!
I've published 3.4.0-rc1 on nuget.org:
https://www.nuget.org/packages/Gremlin.Net/3.4.0-rc1
It's ok to maintain RC for historical reasons :)
El lun., 2 jul. 2018 a las 13:10, Stephen Mallette (<sp...@gmail.com>)
escribió:
> Since you have access to the node repo, I see no reason not to give you
> access to the nuget one as well - invitation sent.
>
> > For next time, shouldn't we use "alpha/beta" instead of "rc"? rc
> denotes code
> completion, no further API changes.
>
> I think we've taken a fairly loose meaning of "release candidate" here in
> TinkerPop over the years. Given that we've done so many "release candidate"
> releases at this point, I'd say we just stick with the "rc" concept rather
> than try to introduce something new now, but if folks think it's creating
> confusion somehow, I guess I don't mind changing next time.
>
>
>
> On Mon, Jul 2, 2018 at 6:56 AM Jorge Bay Gondra <jo...@gmail.com>
> wrote:
>
> > I've published 3.4.0-rc1 on npm:
> > https://www.npmjs.com/package/gremlin?activeTab=versions
> >
> > I don't have access to publish Gremlin.Net on nuget.org, can anyone
> grant
> > me access?
> >
> > El lun., 2 jul. 2018 a las 11:45, Jorge Bay Gondra (<
> > jorgebaygondra@gmail.com>) escribió:
> >
> > > About npm, within the "latest" distribution tag
> > > <https://docs.npmjs.com/cli/dist-tag>, it sorts by date on their web
> UI
> > > but the dependencies are resolved correctly according to semver and
> > > tilde/caret notations, so there isn't much to worry about except that
> the
> > > latest shown on the website is not *the* latest :)
> > > The most used notation on node.js to note prereleases is x.y.z-beta1 /
> > x.y.z-rc1,
> > > there is more info here:
> > > https://docs.npmjs.com/misc/semver#prerelease-identifiers
> > >
> > > I'll deploy 3.4.0-rc1 to npm on the "beta" distribution tag, and
> > 3.4.0-rc1
> > > on nuget.org.
> > >
> > > For next time, shouldn't we use "alpha/beta" instead of "rc"? rc
> denotes
> > > code completion, no further API changes.
> > >
> > > El vie., 29 jun. 2018 a las 21:50, Stephen Mallette (<
> > spmallette@gmail.com>)
> > > escribió:
> > >
> > >> For those interested in doing some development/testing against Python
> > >> 3.4.0rc1 is out there on pypi:
> > >>
> > >> https://pypi.org/project/gremlinpython/3.4.0rc1/
> > >>
> > >> Jorge, I'll leave the .NET and JS to you. Just to be clear, there is
> no
> > >> need to commit anything back to git in terms of this release
> candidate.
> > >> Just make your edits locally and deploy.
> > >>
> > >> Also, I'll make an additional quesiton about how NPM works.....For
> .NET
> > we
> > >> should deploy the version "3.4.0-rc1", but what is the notion of a
> > >> "release
> > >> candidate" in JS terminology? is it also "3.4.0-rc1" or is it like
> > python
> > >> with "3.4.0rc1" or something else?
> > >>
> > >>
> > >>
> > >> On Fri, Jun 29, 2018 at 11:37 AM Stephen Mallette <
> spmallette@gmail.com
> > >
> > >> wrote:
> > >>
> > >> > yeah - we could have done that earlier in the week. i just tagged
> the
> > >> > current master at 3.4.0-rc1
> > >> >
> > >> > https://github.com/apache/tinkerpop/tree/3.4.0-rc1
> > >> >
> > >> > so you can check that tag out and go from there. I can do python
> later
> > >> in
> > >> > the day.
> > >> >
> > >> > By the way, I have a question about npm:
> > >> >
> > >> > https://www.npmjs.com/package/gremlin
> > >> >
> > >> > it seems like npm does not sort by the most recent version number -
> it
> > >> > sorts by date deployed (note that the "current" version is
> 3.2.9)...is
> > >> that
> > >> > right? that doesn't affect the "current" version downloaded does it?
> > can
> > >> > that be changed somehow or do we just need to be careful in how we
> > >> deploy
> > >> > so that our oldest versions go up first?
> > >> >
> > >> > Lastly, just a reminder to everyone, that this 3.4.0-rc1 is just a
> > >> > development release for very early testing purposes. We aren't
> > promoting
> > >> > this convenience release in any way.
> > >> >
> > >> >
> > >> >
> > >> > On Fri, Jun 29, 2018 at 11:25 AM Jorge Bay Gondra <
> > >> > jorgebaygondra@gmail.com> wrote:
> > >> >
> > >> >> It looks like there isn't any concerns, can we move forward by
> > >> releasing
> > >> >> them?
> > >> >>
> > >> >> I can publish Node.js package and .NET package, if needed. I'm not
> > >> >> confident enough to do it for pypi, tho :)
> > >> >>
> > >> >> El sáb., 23 jun. 2018 a las 12:21, Stephen Mallette (<
> > >> >> spmallette@gmail.com>)
> > >> >> escribió:
> > >> >>
> > >> >> > I don't have a problem with doing that. Indeed we have JVM
> > snapshots
> > >> >> > deployed for 3.4.0 on Apache Snapshots Repo, so it makes sense to
> > >> have
> > >> >> dev
> > >> >> > artifacts deployed for the testing purposes for GLVs. Let's wait
> > the
> > >> >> > standard 72 hours for any concerns and then get some release
> > >> candidates
> > >> >> > released.
> > >> >> >
> > >> >> > On Fri, Jun 22, 2018 at 9:50 AM Jorge Bay Gondra <
> > >> >> jorgebaygondra@gmail.com
> > >> >> > >
> > >> >> > wrote:
> > >> >> >
> > >> >> > > Hi,
> > >> >> > > It would be nice to have public alpha/beta releases of the 3.4
> > >> GLVs to
> > >> >> > > start trying out the 3.4 branch.
> > >> >> > >
> > >> >> > > If needed, I could take the work of publishing the node.js
> > package
> > >> for
> > >> >> > this
> > >> >> > > prerelease.
> > >> >> > >
> > >> >> > > wdyt?
> > >> >> > > Jorge
> > >> >> > >
> > >> >> >
> > >> >>
> > >> >
> > >>
> > >
> >
>
Re: [Discuss] 3.4.0 GLV packages
Posted by Stephen Mallette <sp...@gmail.com>.
Since you have access to the node repo, I see no reason not to give you
access to the nuget one as well - invitation sent.
> For next time, shouldn't we use "alpha/beta" instead of "rc"? rc denotes code
completion, no further API changes.
I think we've taken a fairly loose meaning of "release candidate" here in
TinkerPop over the years. Given that we've done so many "release candidate"
releases at this point, I'd say we just stick with the "rc" concept rather
than try to introduce something new now, but if folks think it's creating
confusion somehow, I guess I don't mind changing next time.
On Mon, Jul 2, 2018 at 6:56 AM Jorge Bay Gondra <jo...@gmail.com>
wrote:
> I've published 3.4.0-rc1 on npm:
> https://www.npmjs.com/package/gremlin?activeTab=versions
>
> I don't have access to publish Gremlin.Net on nuget.org, can anyone grant
> me access?
>
> El lun., 2 jul. 2018 a las 11:45, Jorge Bay Gondra (<
> jorgebaygondra@gmail.com>) escribió:
>
> > About npm, within the "latest" distribution tag
> > <https://docs.npmjs.com/cli/dist-tag>, it sorts by date on their web UI
> > but the dependencies are resolved correctly according to semver and
> > tilde/caret notations, so there isn't much to worry about except that the
> > latest shown on the website is not *the* latest :)
> > The most used notation on node.js to note prereleases is x.y.z-beta1 /
> x.y.z-rc1,
> > there is more info here:
> > https://docs.npmjs.com/misc/semver#prerelease-identifiers
> >
> > I'll deploy 3.4.0-rc1 to npm on the "beta" distribution tag, and
> 3.4.0-rc1
> > on nuget.org.
> >
> > For next time, shouldn't we use "alpha/beta" instead of "rc"? rc denotes
> > code completion, no further API changes.
> >
> > El vie., 29 jun. 2018 a las 21:50, Stephen Mallette (<
> spmallette@gmail.com>)
> > escribió:
> >
> >> For those interested in doing some development/testing against Python
> >> 3.4.0rc1 is out there on pypi:
> >>
> >> https://pypi.org/project/gremlinpython/3.4.0rc1/
> >>
> >> Jorge, I'll leave the .NET and JS to you. Just to be clear, there is no
> >> need to commit anything back to git in terms of this release candidate.
> >> Just make your edits locally and deploy.
> >>
> >> Also, I'll make an additional quesiton about how NPM works.....For .NET
> we
> >> should deploy the version "3.4.0-rc1", but what is the notion of a
> >> "release
> >> candidate" in JS terminology? is it also "3.4.0-rc1" or is it like
> python
> >> with "3.4.0rc1" or something else?
> >>
> >>
> >>
> >> On Fri, Jun 29, 2018 at 11:37 AM Stephen Mallette <spmallette@gmail.com
> >
> >> wrote:
> >>
> >> > yeah - we could have done that earlier in the week. i just tagged the
> >> > current master at 3.4.0-rc1
> >> >
> >> > https://github.com/apache/tinkerpop/tree/3.4.0-rc1
> >> >
> >> > so you can check that tag out and go from there. I can do python later
> >> in
> >> > the day.
> >> >
> >> > By the way, I have a question about npm:
> >> >
> >> > https://www.npmjs.com/package/gremlin
> >> >
> >> > it seems like npm does not sort by the most recent version number - it
> >> > sorts by date deployed (note that the "current" version is 3.2.9)...is
> >> that
> >> > right? that doesn't affect the "current" version downloaded does it?
> can
> >> > that be changed somehow or do we just need to be careful in how we
> >> deploy
> >> > so that our oldest versions go up first?
> >> >
> >> > Lastly, just a reminder to everyone, that this 3.4.0-rc1 is just a
> >> > development release for very early testing purposes. We aren't
> promoting
> >> > this convenience release in any way.
> >> >
> >> >
> >> >
> >> > On Fri, Jun 29, 2018 at 11:25 AM Jorge Bay Gondra <
> >> > jorgebaygondra@gmail.com> wrote:
> >> >
> >> >> It looks like there isn't any concerns, can we move forward by
> >> releasing
> >> >> them?
> >> >>
> >> >> I can publish Node.js package and .NET package, if needed. I'm not
> >> >> confident enough to do it for pypi, tho :)
> >> >>
> >> >> El sáb., 23 jun. 2018 a las 12:21, Stephen Mallette (<
> >> >> spmallette@gmail.com>)
> >> >> escribió:
> >> >>
> >> >> > I don't have a problem with doing that. Indeed we have JVM
> snapshots
> >> >> > deployed for 3.4.0 on Apache Snapshots Repo, so it makes sense to
> >> have
> >> >> dev
> >> >> > artifacts deployed for the testing purposes for GLVs. Let's wait
> the
> >> >> > standard 72 hours for any concerns and then get some release
> >> candidates
> >> >> > released.
> >> >> >
> >> >> > On Fri, Jun 22, 2018 at 9:50 AM Jorge Bay Gondra <
> >> >> jorgebaygondra@gmail.com
> >> >> > >
> >> >> > wrote:
> >> >> >
> >> >> > > Hi,
> >> >> > > It would be nice to have public alpha/beta releases of the 3.4
> >> GLVs to
> >> >> > > start trying out the 3.4 branch.
> >> >> > >
> >> >> > > If needed, I could take the work of publishing the node.js
> package
> >> for
> >> >> > this
> >> >> > > prerelease.
> >> >> > >
> >> >> > > wdyt?
> >> >> > > Jorge
> >> >> > >
> >> >> >
> >> >>
> >> >
> >>
> >
>
Re: [Discuss] 3.4.0 GLV packages
Posted by Jorge Bay Gondra <jo...@gmail.com>.
I've published 3.4.0-rc1 on npm:
https://www.npmjs.com/package/gremlin?activeTab=versions
I don't have access to publish Gremlin.Net on nuget.org, can anyone grant
me access?
El lun., 2 jul. 2018 a las 11:45, Jorge Bay Gondra (<
jorgebaygondra@gmail.com>) escribió:
> About npm, within the "latest" distribution tag
> <https://docs.npmjs.com/cli/dist-tag>, it sorts by date on their web UI
> but the dependencies are resolved correctly according to semver and
> tilde/caret notations, so there isn't much to worry about except that the
> latest shown on the website is not *the* latest :)
> The most used notation on node.js to note prereleases is x.y.z-beta1 / x.y.z-rc1,
> there is more info here:
> https://docs.npmjs.com/misc/semver#prerelease-identifiers
>
> I'll deploy 3.4.0-rc1 to npm on the "beta" distribution tag, and 3.4.0-rc1
> on nuget.org.
>
> For next time, shouldn't we use "alpha/beta" instead of "rc"? rc denotes
> code completion, no further API changes.
>
> El vie., 29 jun. 2018 a las 21:50, Stephen Mallette (<sp...@gmail.com>)
> escribió:
>
>> For those interested in doing some development/testing against Python
>> 3.4.0rc1 is out there on pypi:
>>
>> https://pypi.org/project/gremlinpython/3.4.0rc1/
>>
>> Jorge, I'll leave the .NET and JS to you. Just to be clear, there is no
>> need to commit anything back to git in terms of this release candidate.
>> Just make your edits locally and deploy.
>>
>> Also, I'll make an additional quesiton about how NPM works.....For .NET we
>> should deploy the version "3.4.0-rc1", but what is the notion of a
>> "release
>> candidate" in JS terminology? is it also "3.4.0-rc1" or is it like python
>> with "3.4.0rc1" or something else?
>>
>>
>>
>> On Fri, Jun 29, 2018 at 11:37 AM Stephen Mallette <sp...@gmail.com>
>> wrote:
>>
>> > yeah - we could have done that earlier in the week. i just tagged the
>> > current master at 3.4.0-rc1
>> >
>> > https://github.com/apache/tinkerpop/tree/3.4.0-rc1
>> >
>> > so you can check that tag out and go from there. I can do python later
>> in
>> > the day.
>> >
>> > By the way, I have a question about npm:
>> >
>> > https://www.npmjs.com/package/gremlin
>> >
>> > it seems like npm does not sort by the most recent version number - it
>> > sorts by date deployed (note that the "current" version is 3.2.9)...is
>> that
>> > right? that doesn't affect the "current" version downloaded does it? can
>> > that be changed somehow or do we just need to be careful in how we
>> deploy
>> > so that our oldest versions go up first?
>> >
>> > Lastly, just a reminder to everyone, that this 3.4.0-rc1 is just a
>> > development release for very early testing purposes. We aren't promoting
>> > this convenience release in any way.
>> >
>> >
>> >
>> > On Fri, Jun 29, 2018 at 11:25 AM Jorge Bay Gondra <
>> > jorgebaygondra@gmail.com> wrote:
>> >
>> >> It looks like there isn't any concerns, can we move forward by
>> releasing
>> >> them?
>> >>
>> >> I can publish Node.js package and .NET package, if needed. I'm not
>> >> confident enough to do it for pypi, tho :)
>> >>
>> >> El sáb., 23 jun. 2018 a las 12:21, Stephen Mallette (<
>> >> spmallette@gmail.com>)
>> >> escribió:
>> >>
>> >> > I don't have a problem with doing that. Indeed we have JVM snapshots
>> >> > deployed for 3.4.0 on Apache Snapshots Repo, so it makes sense to
>> have
>> >> dev
>> >> > artifacts deployed for the testing purposes for GLVs. Let's wait the
>> >> > standard 72 hours for any concerns and then get some release
>> candidates
>> >> > released.
>> >> >
>> >> > On Fri, Jun 22, 2018 at 9:50 AM Jorge Bay Gondra <
>> >> jorgebaygondra@gmail.com
>> >> > >
>> >> > wrote:
>> >> >
>> >> > > Hi,
>> >> > > It would be nice to have public alpha/beta releases of the 3.4
>> GLVs to
>> >> > > start trying out the 3.4 branch.
>> >> > >
>> >> > > If needed, I could take the work of publishing the node.js package
>> for
>> >> > this
>> >> > > prerelease.
>> >> > >
>> >> > > wdyt?
>> >> > > Jorge
>> >> > >
>> >> >
>> >>
>> >
>>
>
Re: [Discuss] 3.4.0 GLV packages
Posted by Jorge Bay Gondra <jo...@gmail.com>.
About npm, within the "latest" distribution tag
<https://docs.npmjs.com/cli/dist-tag>, it sorts by date on their web UI but
the dependencies are resolved correctly according to semver and tilde/caret
notations, so there isn't much to worry about except that the latest shown
on the website is not *the* latest :)
The most used notation on node.js to note prereleases is x.y.z-beta1 /
x.y.z-rc1,
there is more info here:
https://docs.npmjs.com/misc/semver#prerelease-identifiers
I'll deploy 3.4.0-rc1 to npm on the "beta" distribution tag, and 3.4.0-rc1
on nuget.org.
For next time, shouldn't we use "alpha/beta" instead of "rc"? rc denotes
code completion, no further API changes.
El vie., 29 jun. 2018 a las 21:50, Stephen Mallette (<sp...@gmail.com>)
escribió:
> For those interested in doing some development/testing against Python
> 3.4.0rc1 is out there on pypi:
>
> https://pypi.org/project/gremlinpython/3.4.0rc1/
>
> Jorge, I'll leave the .NET and JS to you. Just to be clear, there is no
> need to commit anything back to git in terms of this release candidate.
> Just make your edits locally and deploy.
>
> Also, I'll make an additional quesiton about how NPM works.....For .NET we
> should deploy the version "3.4.0-rc1", but what is the notion of a "release
> candidate" in JS terminology? is it also "3.4.0-rc1" or is it like python
> with "3.4.0rc1" or something else?
>
>
>
> On Fri, Jun 29, 2018 at 11:37 AM Stephen Mallette <sp...@gmail.com>
> wrote:
>
> > yeah - we could have done that earlier in the week. i just tagged the
> > current master at 3.4.0-rc1
> >
> > https://github.com/apache/tinkerpop/tree/3.4.0-rc1
> >
> > so you can check that tag out and go from there. I can do python later in
> > the day.
> >
> > By the way, I have a question about npm:
> >
> > https://www.npmjs.com/package/gremlin
> >
> > it seems like npm does not sort by the most recent version number - it
> > sorts by date deployed (note that the "current" version is 3.2.9)...is
> that
> > right? that doesn't affect the "current" version downloaded does it? can
> > that be changed somehow or do we just need to be careful in how we deploy
> > so that our oldest versions go up first?
> >
> > Lastly, just a reminder to everyone, that this 3.4.0-rc1 is just a
> > development release for very early testing purposes. We aren't promoting
> > this convenience release in any way.
> >
> >
> >
> > On Fri, Jun 29, 2018 at 11:25 AM Jorge Bay Gondra <
> > jorgebaygondra@gmail.com> wrote:
> >
> >> It looks like there isn't any concerns, can we move forward by releasing
> >> them?
> >>
> >> I can publish Node.js package and .NET package, if needed. I'm not
> >> confident enough to do it for pypi, tho :)
> >>
> >> El sáb., 23 jun. 2018 a las 12:21, Stephen Mallette (<
> >> spmallette@gmail.com>)
> >> escribió:
> >>
> >> > I don't have a problem with doing that. Indeed we have JVM snapshots
> >> > deployed for 3.4.0 on Apache Snapshots Repo, so it makes sense to have
> >> dev
> >> > artifacts deployed for the testing purposes for GLVs. Let's wait the
> >> > standard 72 hours for any concerns and then get some release
> candidates
> >> > released.
> >> >
> >> > On Fri, Jun 22, 2018 at 9:50 AM Jorge Bay Gondra <
> >> jorgebaygondra@gmail.com
> >> > >
> >> > wrote:
> >> >
> >> > > Hi,
> >> > > It would be nice to have public alpha/beta releases of the 3.4 GLVs
> to
> >> > > start trying out the 3.4 branch.
> >> > >
> >> > > If needed, I could take the work of publishing the node.js package
> for
> >> > this
> >> > > prerelease.
> >> > >
> >> > > wdyt?
> >> > > Jorge
> >> > >
> >> >
> >>
> >
>
Re: [Discuss] 3.4.0 GLV packages
Posted by Stephen Mallette <sp...@gmail.com>.
For those interested in doing some development/testing against Python
3.4.0rc1 is out there on pypi:
https://pypi.org/project/gremlinpython/3.4.0rc1/
Jorge, I'll leave the .NET and JS to you. Just to be clear, there is no
need to commit anything back to git in terms of this release candidate.
Just make your edits locally and deploy.
Also, I'll make an additional quesiton about how NPM works.....For .NET we
should deploy the version "3.4.0-rc1", but what is the notion of a "release
candidate" in JS terminology? is it also "3.4.0-rc1" or is it like python
with "3.4.0rc1" or something else?
On Fri, Jun 29, 2018 at 11:37 AM Stephen Mallette <sp...@gmail.com>
wrote:
> yeah - we could have done that earlier in the week. i just tagged the
> current master at 3.4.0-rc1
>
> https://github.com/apache/tinkerpop/tree/3.4.0-rc1
>
> so you can check that tag out and go from there. I can do python later in
> the day.
>
> By the way, I have a question about npm:
>
> https://www.npmjs.com/package/gremlin
>
> it seems like npm does not sort by the most recent version number - it
> sorts by date deployed (note that the "current" version is 3.2.9)...is that
> right? that doesn't affect the "current" version downloaded does it? can
> that be changed somehow or do we just need to be careful in how we deploy
> so that our oldest versions go up first?
>
> Lastly, just a reminder to everyone, that this 3.4.0-rc1 is just a
> development release for very early testing purposes. We aren't promoting
> this convenience release in any way.
>
>
>
> On Fri, Jun 29, 2018 at 11:25 AM Jorge Bay Gondra <
> jorgebaygondra@gmail.com> wrote:
>
>> It looks like there isn't any concerns, can we move forward by releasing
>> them?
>>
>> I can publish Node.js package and .NET package, if needed. I'm not
>> confident enough to do it for pypi, tho :)
>>
>> El sáb., 23 jun. 2018 a las 12:21, Stephen Mallette (<
>> spmallette@gmail.com>)
>> escribió:
>>
>> > I don't have a problem with doing that. Indeed we have JVM snapshots
>> > deployed for 3.4.0 on Apache Snapshots Repo, so it makes sense to have
>> dev
>> > artifacts deployed for the testing purposes for GLVs. Let's wait the
>> > standard 72 hours for any concerns and then get some release candidates
>> > released.
>> >
>> > On Fri, Jun 22, 2018 at 9:50 AM Jorge Bay Gondra <
>> jorgebaygondra@gmail.com
>> > >
>> > wrote:
>> >
>> > > Hi,
>> > > It would be nice to have public alpha/beta releases of the 3.4 GLVs to
>> > > start trying out the 3.4 branch.
>> > >
>> > > If needed, I could take the work of publishing the node.js package for
>> > this
>> > > prerelease.
>> > >
>> > > wdyt?
>> > > Jorge
>> > >
>> >
>>
>
Re: [Discuss] 3.4.0 GLV packages
Posted by Stephen Mallette <sp...@gmail.com>.
yeah - we could have done that earlier in the week. i just tagged the
current master at 3.4.0-rc1
https://github.com/apache/tinkerpop/tree/3.4.0-rc1
so you can check that tag out and go from there. I can do python later in
the day.
By the way, I have a question about npm:
https://www.npmjs.com/package/gremlin
it seems like npm does not sort by the most recent version number - it
sorts by date deployed (note that the "current" version is 3.2.9)...is that
right? that doesn't affect the "current" version downloaded does it? can
that be changed somehow or do we just need to be careful in how we deploy
so that our oldest versions go up first?
Lastly, just a reminder to everyone, that this 3.4.0-rc1 is just a
development release for very early testing purposes. We aren't promoting
this convenience release in any way.
On Fri, Jun 29, 2018 at 11:25 AM Jorge Bay Gondra <jo...@gmail.com>
wrote:
> It looks like there isn't any concerns, can we move forward by releasing
> them?
>
> I can publish Node.js package and .NET package, if needed. I'm not
> confident enough to do it for pypi, tho :)
>
> El sáb., 23 jun. 2018 a las 12:21, Stephen Mallette (<spmallette@gmail.com
> >)
> escribió:
>
> > I don't have a problem with doing that. Indeed we have JVM snapshots
> > deployed for 3.4.0 on Apache Snapshots Repo, so it makes sense to have
> dev
> > artifacts deployed for the testing purposes for GLVs. Let's wait the
> > standard 72 hours for any concerns and then get some release candidates
> > released.
> >
> > On Fri, Jun 22, 2018 at 9:50 AM Jorge Bay Gondra <
> jorgebaygondra@gmail.com
> > >
> > wrote:
> >
> > > Hi,
> > > It would be nice to have public alpha/beta releases of the 3.4 GLVs to
> > > start trying out the 3.4 branch.
> > >
> > > If needed, I could take the work of publishing the node.js package for
> > this
> > > prerelease.
> > >
> > > wdyt?
> > > Jorge
> > >
> >
>
Re: [Discuss] 3.4.0 GLV packages
Posted by Jorge Bay Gondra <jo...@gmail.com>.
It looks like there isn't any concerns, can we move forward by releasing
them?
I can publish Node.js package and .NET package, if needed. I'm not
confident enough to do it for pypi, tho :)
El sáb., 23 jun. 2018 a las 12:21, Stephen Mallette (<sp...@gmail.com>)
escribió:
> I don't have a problem with doing that. Indeed we have JVM snapshots
> deployed for 3.4.0 on Apache Snapshots Repo, so it makes sense to have dev
> artifacts deployed for the testing purposes for GLVs. Let's wait the
> standard 72 hours for any concerns and then get some release candidates
> released.
>
> On Fri, Jun 22, 2018 at 9:50 AM Jorge Bay Gondra <jorgebaygondra@gmail.com
> >
> wrote:
>
> > Hi,
> > It would be nice to have public alpha/beta releases of the 3.4 GLVs to
> > start trying out the 3.4 branch.
> >
> > If needed, I could take the work of publishing the node.js package for
> this
> > prerelease.
> >
> > wdyt?
> > Jorge
> >
>
Re: [Discuss] 3.4.0 GLV packages
Posted by Stephen Mallette <sp...@gmail.com>.
I don't have a problem with doing that. Indeed we have JVM snapshots
deployed for 3.4.0 on Apache Snapshots Repo, so it makes sense to have dev
artifacts deployed for the testing purposes for GLVs. Let's wait the
standard 72 hours for any concerns and then get some release candidates
released.
On Fri, Jun 22, 2018 at 9:50 AM Jorge Bay Gondra <jo...@gmail.com>
wrote:
> Hi,
> It would be nice to have public alpha/beta releases of the 3.4 GLVs to
> start trying out the 3.4 branch.
>
> If needed, I could take the work of publishing the node.js package for this
> prerelease.
>
> wdyt?
> Jorge
>