ShreyeshArangath opened a new issue, #1895: URL: https://github.com/apache/auron/issues/1895
**Describe the bug** <!-- A clear and concise description of what the bug is. --> We currently mark issues as stale after 30 days and automatically close them 14 days later: ```yml days-before-issue-stale: 30 days-before-issue-close: 14 ``` This workflow assumes issues are tracked externally (for example, in JIRA), but we are not using JIRA or any other system to track active issues. As a result, user-reported issues that are still valid but have not received recent activity can be automatically marked stale and closed within ~45 days, even though they may not have been triaged or resolved. This risks losing legitimate issues and negatively impacts visibility into active issues. **To Reproduce** N/A <!-- Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error --> **Expected behavior** <!-- A clear and concise description of what you expected to happen. --> We should look into disabling the stale issues similar to how Gluten does it today as it also does not use JIRA to track active issues. **Screenshots** <!-- If applicable, add screenshots to help explain your problem. --> **Additional context** <!-- Add any other context about the problem here. --> -- 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]
