+1 for graduation

On Wed, Jun 12, 2019 at 1:43 PM Gian Merlino <g...@apache.org> wrote:

> In the last few days, website migration to https://druid.apache.org/ and
> content update to comply with https://whimsy.apache.org/pods/project/druid
> have
> been completed! I think this means we are ready to crack on. Would love to
> hear what others think.
>
> On Sat, Jun 8, 2019 at 12:27 AM Gian Merlino <g...@apache.org> wrote:
>
> > Hey Druids,
> >
> > Druid has been in the incubator for a while, and we have done 4 releases
> > so far (0.13.0, 0.14.0, 0.14.1, and 0.14.2) with a 5th on the way. There
> > has been some discussion off-list recently about pushing for graduation
> and
> > it was pointed out that it is way past time to have a discussion about
> > graduation readiness on-list. So the topic of discussion for this thread
> > is: are we ready to graduate?
> >
> > Here are some links I'm aware of that describe what a podling needs to do
> > to be able to graduate.
> >
> > 1) http://incubator.apache.org/projects/druid.html
> > 2) https://incubator.apache.org/guides/graduation.html
> > 3)
> >
> https://incubator.apache.org/policy/incubation.html#graduating_from_the_incubator
> > 4) https://whimsy.apache.org/pods/project/druid
> >
> > We have done a lot of the hard stuff already. I think in terms of
> > community robustness and adherence to the Apache Way, we were there
> before
> > we even got into the incubator. Known remaining items (known by me, at
> > least):
> >
> > - Website migration from http://druid.io/ to https://druid.apache.org/.
> > Current status: full details are in the the "proposed website migration
> > thread", but TLDR is that site migration is almost complete, hopefully
> > within days of being done.
> >
> > - Website content update to match (1) above: not sure if it's being
> worked
> > on, but shouldn't take long. Contribs welcome.
> >
> > I think we are good on other stuff, but I might have missed something so
> > please chime in anyone / everyone. Here's looking forward to graduation!!
> >
>

Reply via email to