wouldnt it be fair to keep the incubator benefit adjectives away from words like reliable and production ready?
If I am not mistaken, almost all of the efforts are around ceremony around the code, not whether it works. In fact the slowing of the community hurts production ness as it is far slower to fix actual bugs in a way people can consume those fixes. It is fair to say incubator helps with process, community, provenance and many other things. however, I dont think it is relevant or even correct to say it helps make the code more reliable in an operations way. On Tue, Jun 4, 2019, 8:54 AM Craig Russell <apache....@gmail.com> wrote: > > > > On Jun 3, 2019, at 5:40 PM, Greg Stein <gst...@gmail.com> wrote: > > > > On Mon, Jun 3, 2019 at 7:24 PM Craig Russell <apache....@gmail.com> > wrote: > > > >>> On Jun 3, 2019, at 2:33 PM, Justin Mclean <jus...@classsoftware.com> > >> wrote: > >> > >> ... > > > >>> I agree, but if you read the disclaimer is says nothing about releases, > >> perhaps that needs to change? > >> > >> Yes, I'd like to change the disclaimer to state that releases cannot be > >> considered completely reliable, should not be depended on for > production, > > > > > > I believe the above two phrases would be unfair to mature projects. In > > fact, to 95% of all the projects that arrive in the Incubator. The > projects > > *are* reliable and *are* used in production. > > Mature projects arrive here and go into incubation. I'd like to see > production cases use the existing mature project distributions and use the > incubator releases as test subjects. YMMV. > > > > The only difference is they are learning how to become an Apache-style > > community. The software doesn't magically "degrade". > > Once the community makes changes to the "mature" software they have in > production, it not-magically does "degrade". > > Maybe you and I have different standards for production. Take a mature > project, add a few hundred lines of code, and it's no longer the mature > project you are using in production. > > Regards, > Craig > > > > > >> might not have passed all normal Apache reviews, etc. > >> > > > > Concur. > > > > > >> I am of the opinion that the board should not need to be involved in > >> telling the incubator what particular release deficiencies can stop > >> releases. The incubator can certainly ask the board for advice on > proposed > >> change to policy. > >> > > > > Concur. > > > > Cheers, > > -g > > Craig L Russell > c...@apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
