Hi all, I’m seeking lazy consensus to add a couple more steps to the Kansan board [1].
1) We need a design review step to make sure that the SIP adheres to patterns of the project, whether it’s before or after a VOTE thread. Right now, I propose we do this after the VOTE to narrow the scope of concern, but later we should consider all SIP proposals if possible. We can do this during the SIP review meeting on the community calendar [2] and async as warranted. 2) Adding a column between “Approved" and In “Development", called “Release Labelled", where all SIPs are given an adjustable release target via a GitHub Label as outlined in the Release Process [3]. [1] https://github.com/orgs/apache/projects/170 [2] https://superset.apache.org/community [3] https://github.com/apache/superset/wiki/Release-Process Thank you! -e- Evan Rusackas Preset | preset.io Apache Superset PMC
