bobbai00 commented on PR #4250: URL: https://github.com/apache/texera/pull/4250#issuecomment-4008881836
> > Dear @parshimers , > > I would like to know if this is a good practice. If so, what should be the email sender for such emails? I searched for things like `[email protected]`, but seems there is no such mechanism. > > Hey Jiadong, I think in general it is a good practice. For some robot emails I usually just make the reply-to address the dev@ address, since that's where it's going. However, I think an even better practice would be making major changes that are backwards-incompatible more of an community decision, taking place on the dev@ list. Take for example SPIP in Spark, or JEP in OpenJDK. In this way, any community member that is following the development of the project wouldn't be surprised that a breaking change was merged, because they would either be involved or at least watching. I have tried to do this in AsterixDB, and to help instill a culture of basically not breaking the userland unless there is a clear consensus as to what should be broken and why, via the APE process. It's definitely not perfect though and takes time, culture is a multifaceted thing that no one person can change. > > Hope that helps, > > * Ian Thank you Ian. In this case, I think we can close this PR and define the protocol similar to Spark's SPIP. -- 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]
