Github user FlorianHockmann commented on the issue:
https://github.com/apache/tinkerpop/pull/600
Ok, so for Java you can simply publish new `SNAPSHOT` packages and clients
will always take the latest version?
That won't work for NuGet as it will first search for the package with the
specified version in its local cache. So a user will always use the first
_version_ of the package with a version as `3.2.5-SNAPSHOT` that was retrieved
from nuget.org. He won't get any updates after that until we publish a package
with a higher version such as `3.2.5-Z`, because he already has the package
with the version `3.2.5-SNAPSHOT` in his cache.
The solution mentioned in that comment suggests that users don't explicitly
specify the version number in their projects. Instead they can specify the
version as `3.2.5-*` (instead of `3.2.5-beta01` for example) which means that
they always get the latest pre-release version, but that still requires later
packages to have a higher version number. (That solution was also specific to
the now obsolete `project.json` project format and I am not sure if it still
works exactly like that.)
So we definitely have to increase the version number somehow when we want
to publish updates. We basically have the following options for that:
1. A fixed tag such as `SNAPSHOT` or `beta` plus a number that has to be
manually incremented each time we change something (to Gremlin-DotNet or
Gremlin-CSharp): `3.2.5-beta01`, `3.2.5-beta02`, ...
2. A fixed tag plus a build tag that is set during the build process (for
example by Travis): `3.2.5-beta-build1234`, `3.2.5-beta-build1235`, ...
xUnit uses a combination of both and also goes through `alpha`, `beta` and
`rc`.
But since there probably won't be that many changes to Gremlin-CSharp or
Gremlin-DotNet my personal preference is that we simply increment a number in
the suffix manually each time a change is merged into the C# GLV branch. So we
could start for example with `3.2.5-beta01`.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
