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 (<spmalle...@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 <spmalle...@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 < > > jorgebaygon...@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 (< > >> spmalle...@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 < > >> jorgebaygon...@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 > >> > > > >> > > >> > > >
