[RESULT][VOTE] Apache AGE Viewer 1.0.0 (rc2) Release
Thanks for the reviews and the votes for Apache AGE Viewer 1.0.0 RC2. Hopefully we will get some binding votes in the next round of voting. 7 +1 Non Bindings Andrew Ko Joe Fagan Eya Badal Josh Innis VUONG QUOC Viet John Gemignani Nicholas Sorrell Thank you. Alex
[RESULTS][VOTE] Apache AGE Viewer 1.0.0 (rc2) Release
Thanks for the reviews and the votes for Apache AGE Viewer 1.0.0 RC2. Hopefully we will get some binding votes in the next round of voting. 7 +1 Non Bindings Andrew Ko Joe Fagan Eya Badal Josh Innis VUONG QUOC Viet John Gemignani Nicholas Sorrell Thank you. Alex
Re: [VOTE] Apache AGE Viewer 1.0.0 (rc2) Release
Thanks. I will now close this vote and results will be sent shortly. Best regards, Alex On 2022/02/26 03:57:26 Alex Kwak wrote: > Dear Apache AGE Community, > > This is an official vote for the Apache AGE Viewer v1.0.0-rc2 that we have > been working toward. > > To learn more about Apache AGE, please see http://age.apache.org/ > > Functionalities included and addressed in this release: > - Graph visualization for AGE. > - Extends edge and vertex point by point. > - Removed AgensGraph trademarks (as discussed in the previous vote email > thread) > > The vote will be open for 72 hours and pass if a majority +1 votes are cast, > with a minimum of 3 +1 votes. > > Please vote > > [ ] +1 Release this package as Apache AGE Viewer v1.0.0 > [ ] 0 I won't get in the way > [ ] -1 Do not release this package because ... > > > The git tag to be discussed and voted upon > https://github.com/apache/incubator-age-viewer/releases/tag/v1.0.0-rc2 > > The git commit hash: > commit 63ed1882e372ef8cdf6677e9850237650e586848 > > The release files, including signatures, digests, etc. can be found at: > https://dist.apache.org/repos/dist/dev/incubator/age/viewer/apache-age-viewer-1.0.0-incubating-rc2/ > > The SHA512 Checksum for these artifacts is: > 683f17b6bfc84d9fd8c88f0856b4dd18fdb24ab429517134880594243601f6810fefe9f7d9da7d5a802e2236622974c4297cee874e0f06685e85a40d5ac90d3d > > Release artifacts are signed with the following key: > https://downloads.apache.org/incubator/age/KEYS > > The fingerprint of key to sign release artifacts: > 0E7F 408D 8C6A 1952 329C B379 D471 FDCE 5F5C 5B82 > > For more information about the contents of this release, see: > https://github.com/apache/incubator-age-viewer/releases/tag/v1.0.0-rc2 > > > > Best regards, > Alex Kwak >
Re: [DISCUSS] AGE Versioning in Master
Yes, It needs. I agree. Alex On 2022/03/02 20:58:28 Josh Innis wrote: > Hi All, > > For every release of AGE we update the version number. The team is > currently researching how to support upgrading between versions and an > issue about the order of updating the version in Master came to our > attention. > > Currently, before we create a release we update the version number. However > we do this at the end of a development of a release cycle rather than at > the beginning. This will become an issue with maintaining our upgrade > scripts going forward. > > So we propose this change to our release cycle: update the version of AGE > in Master at the beginning of a development cycle rather than at the end. > This will allow us to construct the upgrade scripts through the whole > process of the release rather than having to do it all at once in the end. > > For the current release, we just make the change now and follow this > process going forward. > > Thoughts?/Concerns?/Questions? >
Re: [DISCUSS] AGE Versioning in Master
I agree as well. John On Wed, Mar 2, 2022 at 7:07 PM VUONG QUOC Viet wrote: > Hi Josh, > I agree with your idea. > Best regards, > Viet. > > On Thu, Mar 3, 2022, 3:58 AM Josh Innis wrote: > > > Hi All, > > > > For every release of AGE we update the version number. The team is > > currently researching how to support upgrading between versions and an > > issue about the order of updating the version in Master came to our > > attention. > > > > Currently, before we create a release we update the version number. > However > > we do this at the end of a development of a release cycle rather than at > > the beginning. This will become an issue with maintaining our upgrade > > scripts going forward. > > > > So we propose this change to our release cycle: update the version of AGE > > in Master at the beginning of a development cycle rather than at the end. > > This will allow us to construct the upgrade scripts through the whole > > process of the release rather than having to do it all at once in the > end. > > > > For the current release, we just make the change now and follow this > > process going forward. > > > > Thoughts?/Concerns?/Questions? > > >
