Re: [DISCUSS] Apache AGE (incubating) Release 0.6.0

[Andrew Ko]

+1
Looks good
Thank you




2021년 11월 13일 (토) 오전 6:11, Nicholas Sorrell 님이 작성:

> +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.
> >
> > [ ] +1 Release this package as Apache AGE 0.6.0
> > [ ] -1 Do not release this package because ...
> >
> > To learn more about Apache AGE, please see http://age.apache.org/
> >
> > *Functionalities included and addressed in this release:*
> > - Add VLE SRF (Set Returning Function).
> > - Fix Vertex, Edge, and Path serialization bug (AGE2-307)
> > - Fix CREATE passback bug (AGE2-337).
> > - Fix CREATE transaction block bug (AGE2-345).
> > - Fix parallel build errors.
> > - Fix Travis CI compiler warnings.
> >
> > *
> > *The git tag to be discussed and voted upon:*
> > https://github.com/apache/incubator-age/releases/tag/v0.6.0
> >
> > *The git commit hash:*
> > commit 0dfb741276d5177c2f7beb260634bef21e880386
> >
> > *The release files for 0.6.0, can be found at:*
> > https://dist.apache.org/repos/dist/dev/incubator/age/0.6.0.rc0/
> >
> > *The signatures, files, etc. can be found at:*
> > https://dist.apache.org/repos/dist/dev/incubator/age/
> >
> > *Signatures used for AGE RCs can be found in this file:*
> > https://dist.apache.org/repos/dist/dev/incubator/age/KEYS
> >
> > *The fingerprint of key to sign release artifacts:*
> > 4D57 8595 934A 64F4 8DD9  B39C 7FAD 0CDD C278 09E8
> >
> > *For information about the contents of this release, see:*
> > https://github.com/apache/incubator-age/releases/tag/v0.6.0
> >
> > Thank you for your time.
> > Josh Innis
> >
> >
>
>

Re:Apache AGE (Incubating) - Community Graduation Vote

[Juan Pan]

Hi,


19 months is not a short phase. I am inclined to this graduation proposal and 
still well suggest firstly finishing the 0.6 release. The reason is that there 
are only 3 Apache releases during the incubator, and some issues are 
suspending. 0.6 release will be a positive sign that this community is able to 
run independently.


Best
Trista


--
Juan Pan(Trista) Twitter: @tristaZero


On 11/9/2021 12:31，Eya Badal wrote：
Hi AGE community and Mentors,

Since entering incubation 18 months ago in April 2020 and with five
versions of AGE released, and 0.6.0 imminent, it's fair to say the AGE
community has demonstrated its ability to build software releases the
Apache Way.

We have prepared an assessment of the Apache AGE podling’s maturity, meant
to help inform the decision (of the mentors, community, Incubator PMC, and
ASF Board of Directors) to graduate it as a top-level Apache project. We
used the ASF project maturity model

to evaluate the Apache AGE project and assess itself as having no major
areas for concern. The assessment can be found at the Apache AGE website
 under the COMMUNITY menu.

In addition to building and releasing software, the community has grown the
Apache AGE project in other areas.


-

There have been 64 unique contributors across the AGE and the subproject
AGE Viewer. These Contributors have raised >170 issues or pull requests.
-

We have been addressing Github issues since the start but timeliness was
an issue. In April we created our internal SLA to categorise (label),
assign, and respond to issue and pull requests. Since April, 95% are
responded within 72 hours (80% of issues are responded to within 24 hrs).
-

Contributions span more than 20 countries across the globe - Belarus,
Belgium, China, France, Germany, Ireland, Israel, Italy, Luxembourg,
Netherlands, Russia, South Korea, Thailand, UK, Ukraine, USA, and Vietnam.
-

We have amassed positive comments throughout and gathered >470 stars.
-

We have committers from 4 different companies.


AGE mentors, what is your opinion on this?

Do you agree that we are ready to graduate?

Are there any remaining issues that we can improve on?

If we can capture your issues of concern we can then work those issues to
resolution.

Your feedback would be very much appreciated!

Regards,

Eya