Julian, The release I was referring to in our report was 0.4.5a56 which is an alpha release. Would specifying this in the report make it more accurate? If not, I can remove that from the report altogether. Thanks for your feedback.
Stepheny From: Julian Hyde <jh...@apache.org> Date: Wednesday, November 2, 2022 at 11:22 AM To: dev@sdap.apache.org <dev@sdap.apache.org> Subject: [EXTERNAL] Re: November Apache SDAP report draft Thanks for writing and submitting the report, Stepheny. I signed off and made the following comments: > The report says that there has been a release. I dispute > that. There is no release vote on dev@, no mention of the > release on dev@, nothing on announce@, and no downloads page. > > As far as I can tell, this project has never made an Apache > release. > > SDAP's number 1 problem is their use of dev@. There is activity > in the project (including commit messages going to dev@) but > questions asked on dev@ go unanswered, and therefore > conversations don't happen. Even the report is drafted on > private@ rather than dev@. I think I can work with SDAP and get > them to graduate but only if they engage on dev@. > > I have given notice that I will resign as a mentor by Dec 31st if > I don't see activity, namely a plan to graduate, and activity to > carry out that plan. Julian On 2022/11/02 00:57:44 "Perez, Stepheny K (US 398F)" wrote: > Hello, > > Attached you will find a draft of the November 2022 Apache SDAP report. In > this report, I’ve included details about what steps we still need to take > before graduating and a target date for graduating. Please provide feedback > on the contents, as I’ll be submitting the reporting today at C.O.B. > > Thank you! > Stepheny > >
