gracecluvohio commented on PR #4250: URL: https://github.com/apache/texera/pull/4250#issuecomment-4009078704
> > Hello @chenlica and @bobbai00 , > > What do you think about making the SQL DDL changes a community wide discussion instead? Perhaps we could notify developers via the dev mail list _before_ a DDL change is merged, rather than after. That way developers have a say, or are at least aware, before a breaking change is merged. > > Hi @gracecluvohio and @chenlica , > > According to Ian's comment, I am leaning towards closing this PR and defining something similar to https://spark.apache.org/improvement-proposals.html. For all the changes that are non-backward-compatible, we should let developers follow this protocol. > > What do you guys think? I'm not sure. On one hand, I think having a proposal system could be helpful to ensure that developers have a say in breaking changes. However, it also seems like a very involved, lengthy process for PRs with small DDL changes. I'm not sure if the whole community needs to be involved in the review of such PRs; they just need to be notified of one, so they can keep their local instance operational. I'd like to hear what @chenlica thinks though. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
