hudi-bot opened a new issue, #14887:
URL: https://github.com/apache/hudi/issues/14887
Improvement ideas
* it should periodically scan GH issues and auto close upon some condition
(e.g. “block on user” and no response from last comment in 30 days)
* it should help auto close or follow up on JIRAs upon some condition (yet
to define)
* PR test build is a pull model by periodic scanning PRs; better to use a
push model to react to PR updates immediately like to trigger a build. Reduce a
few min wait time
* for every new commit, it should append a comment show new report
“pending”; it should also update the same comment to show report results once
build is done
* a new commit or a force push should cancel previous build job and start a
new job
* users don’t need to use {{@hudi-bot run azure}}
* it can also report back codecov reports once integrate with codecov in
the mirror repo
## JIRA info
- Link: https://issues.apache.org/jira/browse/HUDI-2575
- Type: Epic
- Fix version(s):
- 1.1.0
---
## Comments
18/Oct/21 15:50;xushiyan;from [~codope]
{quote}c) Apart from what you have already listed, may I also suggest a
[cc-bot|https://github.com/pytorch/pytorch/issues/24422] by which not just
PMC/committers but anyone in the community interested in following some story
gets tagged on the issue automatically.
PyTorch is a really big open source project. I found the following two posts
a good-read for maintaining such big projects in general.More on
principles/philosophy:
[https://soumith.ch/posts/2021/02/growing-opensource/]More on scaling
operationally: [http://blog.ezyang.com/2021/01/pytorch-open-source-process/]
{quote};;;
---
19/Oct/21 14:59;xushiyan;[~shivnarayan] Another point: if Jira components
and labels aligned with GH labels (e.g. Jira component "spark" => GH label
"c:spark" ) then filing Jira can be automated by the bot too. We can label GH
issue with "jira-filing" then bot may just auto-file with all info from the GH
issue (labels, title and link);;;
--
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]
