Based on what I've seen from the project for the last couple of years, here's my short synopsis of the status wrt graduating.
To graduate, a project must cut an official release. This is the main point holding SDAP back from graduation. Apache as an organization was designed for creating and releasing Java projects, SDAP is a Python project. (There are Python projects elsewhere in the ASF, but I will stand by my original statement, that Java is first class, everything else should adapt to Java). SDAP as a community has focused the majority of its cycles to supporting existing deployments of their software as opposed to refactoring to conform with ASF things. I don't think there exists undue stress from the ASF to conform- just a lack of documentation for non-Java paths. My recommendation in terms of cutting a release (and thus removing the largest hurdle to graduation) would be to 1. call a code freeze 2. tag / create a zip file of the current code base. 3. have various PPMC member test the code (what ever that means in relation to SDAP) 4. vote 5.manually push the zip file to whatever repository that is needed. I know there are lots of maven plugins that automate #5, that will be effectively unusable since this isn't a Java project. Just get ahold of someone at Infra and ask them what you need to do to manually release a source tar ball. Then document it, maybe put it on the website- and make a plan to do it again once a year to keep the board off your back. I know your real life users don't care about official releases anyway, so it's just a formality that has to happen every so often. My .02 tg On Thu, Oct 13, 2022 at 1:17 PM Justin Mclean <[email protected]> wrote: > Hi Julian, > > Thanks for reaching out to the SDAP project, I also think it time this > project needs to consider graduating or the other option is retirement from > the ASF. > > Kind Regards, > Justin >
