I’d like to point out the while it is convenient, as per policy, an Apache
project should not have “official” or dev binaries that created nightly or
similarly that is not an approved, voted release.
In other words, dev tag on development branch should be clearly marked as not
an official
jrgemignani commented on issue #41:
URL: https://github.com/apache/incubator-age/issues/41#issuecomment-794493972
Okay, so I was incorrect - sort of - when I said that the load command
didn't need to be used after the first time (with the create extension),...
The first time you
pdpotter opened a new issue #41:
URL: https://github.com/apache/incubator-age/issues/41
After creating a new database connection, the first cypher query results in
a `ERROR: unhandled cypher(cstring) function call error`. This error does not
occur on subsequent cypher queries, or if a
eyab merged pull request #7:
URL: https://github.com/apache/incubator-age-website/pull/7
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to
Because Docker builds can support multiple tags, I would propose that the
default `latest` tag point to the latest stable release and that version
tagging becomes explicit (i.e., 0.3.0) in the future AGE Docker images. I would
also propose a `dev` tag that points to the head of the chosen
