GitHub user WangzJi added a comment to the discussion: Proposal: Adopt GitHub CI to Auto-Generate Changelogs
Thank you for raising this important concern, @YongGoose! You're absolutely right to be cautious about adopting tools that might have maintenance issues. This is a valid point that deserves careful consideration. ### Addressing the Maintenance Concern While release-drafter hasn't seen recent commits, it's worth noting that: 1. **Mature and stable**: The tool has been around for years and is quite mature. Many projects continue using it successfully despite the slower update pace. 2. **Active usage**: Several major projects still rely on it: [apache/maven](https://github.com/apache/maven) [jenkinsci/jenkins](https://github.com/jenkinsci/jenkins) 3. **Simple functionality**: The core functionality is relatively straightforward - it's essentially template-based text generation, which is less likely to break with GitHub API changes. ### Alternative Solutions That said, your point about exploring alternatives is excellent. Here are some actively maintained options: - [release-please(Google)](https://github.com/googleapis/release-please) - Conventional commits + automatic versioning - GitHub's built-in Release Notes - Zero maintenance, native integration ### Proposed Path Forward Given your feedback, I suggest we evaluate multiple options: - Phase 1: Research and prototype with 2-3 different tools - Phase 2: Test them on a few minor releases - Phase 3: Choose the best fit based on our workflow and maintenance preferences Would you be interested in helping evaluate these alternatives? I think having multiple perspectives would lead to a better decision for the project. What are your thoughts on this approach? Any particular tools from this list that seem more appealing from a maintenance perspective? GitHub link: https://github.com/apache/incubator-seata/discussions/7441#discussioncomment-13478364 ---- This is an automatically sent email for dev@seata.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@seata.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@seata.apache.org For additional commands, e-mail: dev-h...@seata.apache.org
