Yicong-Huang commented on PR #3812: URL: https://github.com/apache/texera/pull/3812#issuecomment-3369000235
good question! However I think we should start to use versions to track instead of commits. Because when reporting bugs, the reporter could be developers and users. And even for developers, one may not know the root cause yet, thus it's more make sense to report a coarse grained version, instead of a fine grained commit. I can think of the following: 1. Add an entry for pre-release versions, for example, our current master always refers to the next pre-release version (I.e., `1.1.0-incubating` for now). One can choose this pre-release version to report for master. 2. Add an optional field of commit hash, if developer knows which commit has issue, he/she can include it in the report. Users or developers who do not know exact commit has the issue, can just ignore it. What do you think? -- 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]
