+1 (binding)
Checked high level:
- Signature and Hash
- Tags and Links
- LICENSE and NOTICE
- No unexpected binary files
- No unexpected files between git repo/apache release and all file
checksums match
Performed smoke test which includes:
- Build Dockerfile (which
+1 (binding)
Checked high level:
- Signature and Hash
- Tags and Links
- LICENSE and NOTICE
- No unexpected binary files
- No unexpected files between git repo/apache release and all file
checksums match
Performed smoke test which includes:
- Build Dockerfile (which
+1 (binding)
Checked high level:
- Signature and Hash
- Tags and Links
- LICENSE and NOTICE
- No unexpected binary files
- No unexpected files between git repo/apache release and all file
checksums match
Performed smoke test which includes:
- Build Dockerfile (which
+1 (binding)
Checked high level (seen here
https://github.com/sorrell/apache_age_release_verification/actions/runs/6101578970/job/16558208166):
- Signature and Hash
- Tags and Links
- LICENSE and NOTICE
- No unexpected binary files
- No unexpected files between git
+1 (binding)
Checked:
- Signature and Hash
- Tags and Links
- LICENSE and NOTICE
- No unexpected binary files
- No unexpected files between git repo/apache release and all file
checksums match
Performed smoke test which includes:
- Build Dockerfile (which builds
+1 (binding)
Checked:
- Signature and Hash
- Tags and Links
- LICENSE and NOTICE
- No unexpected binary files
Performed smoke test which includes:
- Build Dockerfile (which builds project)
- Run Docker image
- Runs commands (create graph/node) via psql
+1 (binding)
Checked:
- Signature and Hash
- Tags and Links
- LICENSE and NOTICE
- No unexpected binary files
Performed smoke test which includes:
- Build Dockerfile (which builds project)
- Run Docker image
- Connect to container, verify age location &
+1 (binding)
Checked:
- Signature and Hash
- Tags and Links
- LICENSE and NOTICE
- No unexpected binary files
- git history verified against RELEASE
Performed smoke test which includes:
- Build Dockerfile (which builds project)
- Run Docker image
-
+1 binding
From: Dehowe Feng
Sent: Tuesday, April 11, 2023 11:22:07 AM
To: dev@age.apache.org
Subject: Re: [VOTE] Apache AGE 1.3.0 Release for PostgreSQL 13
+1 (binding),
Did all of the usual checks, looks good.:
- checked the signature and hash
I’m curious if any experimentation has been done with the `git cherry-pick`
command? This sounds like the ideal use case where it would preserve the
history and give the PR initiator co-authorship. You might have already
explored this, but just wanted to mention it. Here’s a small article
+1
> On Jan 26, 2023, at 16:51, Jasper Blues wrote:
>
> +1 (again)
>
>> On 27 Jan 2023, at 7:14 am, John Gemignani
>> wrote:
>>
>> Dear Apache Community,
>>
>> This is an official *RE-ISSUED* vote for the Apache AGE Release 1.1.1 for
>> PostgreSQL 12.
>>
>> To learn more about Apache
+1
> On Jan 26, 2023, at 16:07, Jasper Blues wrote:
>
> +1
>
>> On 27 Jan 2023, at 7:05 am, John Gemignani
>> wrote:
>>
>> Dear Apache Community,
>>
>> This is an official vote for the Apache AGE 1.2.0 Release for PostgreSQL 11.
>>
>> To learn more about Apache AGE, please see
+1
> On Nov 7, 2022, at 04:11, Pieterjan De Potter
> wrote:
>
> +1
>
>> On 04.11.22 19:40, John Gemignani wrote:
>> Dear Apache Community,
>> We are now opening the vote for the Apache AGE release 1.1.0 for PostgreSQL
>> 12 (PG12).
>> To learn more about Apache AGE, please see
+1, well done!
--
Nick Sorrell
From: Josh Innis
Sent: Friday, August 12, 2022 11:40 AM
To: dev@age.apache.org
Subject: Re: [VOTE] Release Apache AGE 1.1.0-rc0
+1 (Binding)
All links are valid
Commit hash is correct
verified the hash and signature
On Fri,
Docker Hub supports building in two ways:
1. Branch name
2. Tagging
A combination of the two could be effective.
Since they will live in separate branches, option 1 of building on any commit
to that branch is a straightforward. However, building on any/every commit to a
branch can lead to
unication and verification. We
> need to make sure everyone understands that anything that modifies the
> master repository is communicated and okayed by others.
>
> John
>
> On Wed, Apr 6, 2022 at 9:17 AM Nicholas Sorrell wrote:
>
> > Hi John,
> >
> > Th
tps://issues.apache.org/jira/browse/INFRA-22727
only allows for this regex: /^v(\d+\.\d+\.\d+)$” Does this mean the rc.*
tags are not included?
On Wed, Apr 6, 2022 at 9:17 AM Nicholas Sorrell wrote:
> Hi John,
>
> The automated email is certainly misleading, as I don't know where it's
> ge
a tag added to tree
Hope this helps, and happy to answer any other questions.
-Nick
From: John Gemignani
Sent: Wednesday, April 6, 2022 11:52 AM
To: dev@age.apache.org ; Nicholas Sorrell
Cc: comm...@age.apache.org
Subject: Re: [incubator-age] annotated tag v0.7.0
Thanks for the reviews and the votes for Apache AGE 1.0.0-RC1. Below are the
results of the voting.
1 (+1) Binding Vote:
*Trista Pan
5 (+1) Non Binding:
*Josh Innis
*Andrew Ko
*John Gemegnani
*Muhammad Shoib
*VUONG QUOC Viet
valid.
> >
> > [x] LICENSE, NOTICE and DISCLAIMER files are correct.
> >
> > [x] All files have license headers if necessary.
> >
> >
> >
> >
> ------
> > Trista Pan
> >
Dear Apache Community,
This is an official vote for Apache AGE release 1.0.0-rc1.
To learn more about Apache AGE, please see https://age.apache.org/
Functionality included and addressed in this release:
- Add an upgrading SQL script file from 0.5.0 to 0.6.0
- Add upgrading file
0.0-incubating`?
Thanks,
Trista
--
Trista Pan
Twitter & Github: tristaZero
On 03/16/2022 03:03，Nicholas Sorrell wrote：
Dear Apache Community,
This is an official vote for the Apache AGE release 1.0.0 that we ha
Reminder, the vote is scheduled to close in less than 24 hours.
Please vote:
[ ] +1 Release this package as Apache AGE 1.0.0
[ ] 0 I won't get in the way
[ ] -1 Do not release this package because ...
From: Nicholas Sorrell
Sent: Tuesday, March 15, 2022 3:03:00
Dear Apache Community,
This is an official vote for the Apache AGE release 1.0.0 that we have been
working towards.
To learn more about Apache AGE, please see http://age.apache.org/
Functionality included and addressed in this release:
- Add an upgrading SQL script file from 0.5.0 to 0.6.0
Release
Looks good.
+1
On 2022/03/12 19:29:15 Nicholas Sorrell wrote:
> Dear Apache Community,
>
> We would like to discuss the Apache AGE release 1.0.0 that we have been
> working towards.
>
> To learn more about Apache AGE, please see https://age.apache.org/
>
>
Sorry, to DISCUSS
--
Nick Sorrell
513.288.1084
https://cint.io
From: Nicholas Sorrell
Sent: Monday, March 14, 2022 2:34 PM
To: dev@age.apache.org
Subject: Re: [DISCUSS] Apache AGE 1.0.0 Release
Gentle reminder - 24 hours remaining to vote.
--
Nick Sorrell
Gentle reminder - 24 hours remaining to vote.
--
Nick Sorrell
513.288.1084
https://cint.io
From: Nicholas Sorrell
Sent: Saturday, March 12, 2022 2:29 PM
To: dev@age.apache.org
Subject: [DISCUSS] Apache AGE 1.0.0 Release
Dear Apache Community,
We would like
As I was creating the 1.0.0 release, it occurred to me that we could automate
some of these steps needed for releasing. With that in mind, I created
age-release-helper here https://github.com/sorrell/age-release-helper
Right now it automates a few but not all of the steps needed for a release.
Dear Apache Community,
We would like to discuss the Apache AGE release 1.0.0 that we have been working
towards.
To learn more about Apache AGE, please see https://age.apache.org/
Functionality included and addressed in this release:
- Add an upgrading SQL script file from 0.5.0 to 0.6.0
-
+1
From: John Gemignani
Sent: Monday, February 28, 2022 12:13:36 PM
To: dev@age.apache.org
Subject: Re: [VOTE] Apache AGE Viewer 1.0.0 (rc2) Release
+1
On Mon, Feb 28, 2022 at 8:35 AM Josh Innis wrote:
> +1
>
> On Sat, Feb 26, 2022 at 9:20 AM Eya Badal
I think a cleaner model is to use git tags to tag a commit as alpha/beta/rc.
Then there is no question of which hash each branch is on as there aren’t
different branches. Also, the lineage is more easily traceable in a single git
log command.
I think the notes about informing users of what
to their talking points.
> On Feb 10, 2022, at 10:02 PM, Nicholas Sorrell wrote:
>
> All,
>
> I wanted to propose that we overhaul the website
> (https://github.com/apache/incubator-age-website) to make it easier to
> contribute to, easier to modify, more extensible, more a
I agree with this, and further tested your hypothesis on a Neo4j Docker
instance with a (linked below) Python script. I ran multiple tests, up to
10,000 iterations, and it was always right directed.
https://gist.github.com/sorrell/49a8ae02272a93dce893a5492e246426
Nick
I agree with Jasper's response. My preferences would also be the same order:
Try to keep it arbitrary/random, else pick a direction. Option 1 of rejecting
the statement deviates from the spec and creates interoperability issues.
From: Jasper Blues
Sent:
I echo the requests for:
* Support for newer Postgres versions (and upgrades) - this seems like a really
important feature with PG11 EOL in Nov-2023. So not around the corner, but
certainly on the horizon, and likely a barrier for higher adoption rates.
* Support for indexes - this is also a
+1
--
Nick Sorrell
513.288.1084
https://cint.io
From: Pieterjan De Potter
Sent: Wednesday, January 19, 2022 3:15 AM
To: dev@age.apache.org
Subject: Re: [VOTE] Apache AGE 0.7.0 Release
+1
On 19.01.22 00:37, Dehowe Feng wrote:
> Dear Apache Community,
>
> This
+1
And kudos to Josh and Alex for getting those issues resolved so quickly.
--
Nick Sorrell
513.288.1084
https://cint.io
From: Joe Fagan
Sent: Wednesday, January 5, 2022 11:54 PM
To: dev@age.apache.org
Subject: Re: [VOTE] Release Apache AGE Viewer
I have a few questions:
* Should this file be included in the repo? It seems to be specific to
Agensgraph.
https://github.com/apache/incubator-age-viewer/blob/main/frontend/src/documents/tutorial/northwind.jsx
* The SVGs referenced in this file
+1. The community and product growth over the past year have been impressive
and I am excited to see the future growth.
--
Nick Sorrell
513.288.1084
https://cint.io
From: Felix Cheung
Sent: Sunday, December 5, 2021 5:02 PM
To: dev@age.apache.org
Subject: Re:
+1
> On Nov 23, 2021, at 06:31, Kevin Ratnasekera wrote:
>
> +1
>
>> On Tue, Nov 23, 2021 at 4:57 PM Juan Pan wrote:
>>
>> +1, looks like DISCLAIMER-WIP was fixed this time.
>>
>>
>>
>> [x] Download links are valid.
>>
>> [x] Checksums and PGP signatures are valid.
>>
>> [x] LICENSE,
+1. This project has matured a lot and provides the missing link to making
Postgres a one-stop-shop for all database needs. The team has done a great job
of building community around a valuable product. (This message was sent again
because the first didn't make it to lists.apache.org)
On
+1
On 2021/11/10 19:58:06 Josh Innis wrote:
> Dear Apache Community,
>
> Please vote on releasing the following candidate as Apache AGE version 0.6.0.
>
> The vote is open now and until November 13th at 12:00 PM PST and passes if
> a majority +1 votes are cast, with a minimum of 3 +1 votes.
>
> [
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
43 matches
Mail list logo
