Hi PJ, Thanks for raising this – I agree that resolving the rename is key to unblocking graduation, especially given the benefits to releases and IPMC bandwidth.
To move forward: I can prioritize wrapping up the remaining rename tasks this week (ASAP). Once the rename is confirmed, I’d suggest we collectively draft the Fury/Fory Maturity Model using Gravitino’s template as a starting point. >From there, we can align on the graduation vote timeline per the Incubation Guide. Thanks, Shawn On Wed, May 28, 2025 at 6:22 PM PJ Fanning <[email protected]> wrote: > > Hi everyone, > > It would be great to see the project graduate. It would make it easier to do > releases and you would no longer need IPMC approval. There are also new > podlings and new applications to become podlings so freeing up IPMC time > would be appreciated. > > The one thing that delays graduation is getting the project rename done. > > * https://incubator.apache.org/guides/graduation.html > > Example Maturity Model. We would need a Fury/Fory one as part of setting up > the graduation vote. > * > https://cwiki.apache.org/confluence/display/GRAVITINO/Gravitino+Maturity+Model > > Does anyone have any opinions on this? > > Thanks, > PJ > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
