Re: [VOTE] Apache AGE 1.3.0 Release for PostgreSQL 13
- You CANNOT just say, +1 or 0. You need to state what items > you checked. > > If your vote DOES NOT follow the above guidelines or samples below, it may > be thrown out. > > !!! IMPORTANT PLEASE READ !!! > > Please vote as follows - > > +1, Release this package as Apache AGE 1.3.0 for PostgreSQL 13. > 0, I won't get in the way of the vote. > -1, Do not release this package because > > !!! Followed by what you checked !!! > > Sample responses, two for PMCs (binding) and two for regular committers. > These are only samples, do not copy/paste. > Remember, binding is ONLY for PMCs. If you are not a PMC, DO NOT say > binding. If you are a PMC, you must state it. > >+1 (binding) +1 >Checked the following: Checked the following: >- Signature and Hash. - Signature and Hash. >- Tags and Links. - Tags and Links. >- LICENSE and NOTICE. - LICENSE and NOTICE. >- No unexpected binary files. - No unexpected binary files. > > -1, Failed due to 0 (binding) > Checked the following: Checked the following: >- Signature and Hash. - Signature and Hash. >- Tags and Links. - Tags and Links. >- BAD LICENSE and NOTICE. - LICENSE and NOTICE. >- No unexpected binary files. - No unexpected binary files. > > Again, those are just samples for guidance, DO NOT copy/paste. However, > your responses should be similar in form. > > Please note that it is not a good practice to copy/paste someone else's > response, you may inadvertently misrepresent yourself or your vote. > > This vote will be open for 72 hours. > > Thank you for your time. > > John Gemignani > -- Bitnine Global, Inc. - We create value for our clients by connecting the world's data. *Eya Badal Abdisho* Technical Engineer E-mail : eya.abdi...@bitnine.net Mobile : +1 408-966-3301 3945 Freedom Cir., Suite 260, Santa Clara, CA 95054 www.bitnine.net
Re: [VOTE] Apache AGE 1.1.0 for PG12 Release
+1 I checked the following. - PGP Signatures. - SHA512 Checksums. - LICENSE and NOTICE are fine. Thank you for the great release and work. Best regards, On Fri, Nov 4, 2022 at 11:40 AM 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 http://age.apache.org/ > > > > Functionalities included and addressed in this release: > > >- Support for Agtype containment ops and GIN Indices. >- Add CALL [YIELD] grammar rules for the implementation of CALL >procedures. >- VLE path variable integration performance patch. >- Improve WHERE clause performance and support index scans. >- Allow global graph contexts to see currentCommandIds. >- Cache Agtype and GRAPHID OIDs. >- Allow lists and maps to be used in the SET clause. >- Fix bug in aggregate function collect(). >- Fix Bug in WHERE clause and property constraints. >- Fix VLE local cache bug (crash). >- Fix bug where integers were not being serialized correctly when stored >in GIN indices. >- Fix the VLE peek_stack_head routine to return a NULL if the stack is >NULL. >- Fix MERGE visibility in chained commands, SET specifically. >- Fix github issue #212 <https://github.com/apache/age/pull/212> - Add >access operator (->, ->>) to Agtype. >- Fix github issue #220 <https://github.com/apache/age/issues/220> - > fix >local cached contexts for static procedures. >- Fix github issue #224 <https://github.com/apache/age/pull/224> - fix >regression tests to fix issues on mac with trigonometric functions. >- Fix github issue #235 <https://github.com/apache/age/issues/235> - >when MERGE and SET were used together. >- Fix github issue #240 <https://github.com/apache/age/issues/240> - >negative array bounds. >- Fix github issue #240 <https://github.com/apache/age/issues/240> - >negative array bounds - addendum. >- Updated README. > > > * > > > > The git tag to be discussed and voted upon: > > https://github.com/apache/age/releases/tag/PG12/v.1.1.0-rc0 > <https://github.com/apache/age/releases/tag/PG12%2Fv1.1.0-rc0> > > > > The git commit hash: > > > commit 1d9d60197e2cf3fc48aac573278f6f9e173ee78b > > > The release files for 1.1.0, can be found at: > > https://dist.apache.org/repos/dist/dev/age/PG12/1.1.0.rc0 > <https://dist.apache.org/repos/dist/dev/age/PG12/1.1.0.rc0> > > > > Signatures used for AGE RCs can be found in this file: > > https://downloads.apache.org/age/KEYS > <https://downloads.apache.org/age/KEYS> > > > > The fingerprint of key to sign release artifacts: > > > 4293 0603 8E35 AC05 4DBB 4B58 26B6 CD9D CD5B 0045 > > > > For information about the contents of this release, see: > > https://github.com/apache/age/releases/tag/PG12/v1.1.0-rc0 > > > > Please review that everything meets your criteria and vote accordingly. > > > Please vote: > > > [ ] +1 Release this package as Apache AGE 0.7.0 > > [ ] 0 I won't get in the way > > [ ] -1 Do not release this package because ... > > This vote will be open for 72 hours. > > As always, thank you for your time. > > > John Gemignani > -- Bitnine Global, Inc. - We create value for our clients by connecting the world's data. *Eya Badal Abdisho* Technical Engineer E-mail : eya.abdi...@bitnine.net Mobile : +1 408-966-3301 3945 Freedom Cir., Suite 260, Santa Clara, CA 95054 www.bitnine.net
Re: [incubator-age] annotated tag v0.7.0 updated (d0175f4 -> b5cdd67)
Same here. I totally agree. On Wed, Apr 6, 2022 at 10:02 AM John Gemignani wrote: > I totally agree with you Nick. > > John > > On Wed, Apr 6, 2022 at 9:59 AM Nicholas Sorrell wrote: > > > John, > > > > Your concerns are valid and I'm sorry for any confusion I created. > > However, the Developer Guidelines at https://age.apache.org don't > reflect > > the process you'd like to see enforced. We should probably update those > > guidelines to reflect how we'd like the community to operate. > > > > -Nick > > > > > > > > > > From: Eya Badal > > Sent: Wednesday, April 6, 2022 12:54 PM > > To: dev@age.apache.org > > Subject: Re: [incubator-age] annotated tag v0.7.0 updated (d0175f4 -> > > b5cdd67) > > > > Next time, I will open a discussion thread so everyone can have > visibility > > on the steps and actions that need to be taken. > > > > As of now, I believe we need to have a better system to build the docker > > and push it to the docker hub. > > > > Thank you, > > Eya > > > > On 2022/04/06 16:48:47 John Gemignani wrote: > > > My issues are twofold - > > > > > >1. Issues that involve the master repository, like this one, need to > > be > > >addressed or communicated to the entire team. > > >2. We do not delete anything from the master repository unless there > > is > > >a compelling, valid reason. And, deletes, even tags, need to be > > >communicated to the entire team. > > > > > > Both of these basically come down to communication 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, > > > > > > > > The automated email is certainly misleading, as I don't know where > it's > > > > getting the 0.3.0 stuff from. > > > > > > > > Here's the full context of the tagging: > > > > - Eya and I were trying to get the automated build to trigger at > Docker > > > > Hub (https://hub.docker.com/r/apache/age) > > > > - I pushed a v0.7.0 annotated tag (on Saturday 2-APR) on top of the > > > > v0.7.0-rc0 tag (same commit hash (d0175f4)) to trigger the build > > > > - The build did not trigger at Docker Hub, so Eya and I worked > > together to > > > > fix the build trigger at Docker Hub > > > > - To re-trigger the build for v0.7.0, I first had to delete the > > existing > > > > v0.7.0 tag and then push a new one at the same commit hash (d0175f4) > > > > - That tag triggered a successful build at Docker Hub, and the tag > can > > be > > > > viewed here as the most recent tag: > > > > https://github.com/apache/incubator-age/tags > > > > - The release, assets, and source code were not altered in any way, > > this > > > > was only 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 < > > > > n...@cint.io> > > > > Cc: comm...@age.apache.org > > > > Subject: Re: [incubator-age] annotated tag v0.7.0 updated (d0175f4 -> > > > > b5cdd67) > > > > > > > > @Nicholas Sorrell<mailto:n...@cint.io> > > > > > > > > What was done that triggered this? > > > > > > > > John > > > > > > > > On Tue, Apr 5, 2022 at 4:38 PM > > > sorr...@apache.org>> wrote: > > > > This is an automated email from the ASF dual-hosted git repository. > > > > > > > > sorrell pushed a change to annotated tag v0.7.0 > > > > in repository https://gitbox.apache.org/repos/asf/incubator-age.git > > > > > > > > > > > > *** WARNING: tag v0.7.0 was modified! *** > > > > > > > > from d0175f4 (commit) > > > > to b5cdd67 (tag) > > > > tagging d0175f4a2fb03f28c356ea43da3bd48a47f5ef42 (commit) > > > > replaces v0.3.0.rc0-incubating > > > > by Nick Sorrell > > > > on Tue Apr 5 19:37:34 2022 -0400 > > > > > > > > - Log > - > > > > v0.7.0 > > > > > --- > > > > > > > > > > > > No new revisions were added by this update. > > > > > > > > Summary of changes: > > > > > > > > > > > > > > -- Bitnine Global, Inc. - We create value for our clients by connecting the world's data. *Eya Badal Abdisho* Technical Engineer E-mail : eya.abdi...@bitnine.net Mobile : +1 408-966-3301 3945 Freedom Cir., Suite 260, Santa Clara, CA 95054 www.bitnine.net
