[repo-status] Weekly repository status — 2026-08-09 to 2026-08-16 🌟

[github-actions]

Apache CloudStack weekly status

Reporting period: 2026-08-09 through 2026-08-16

CloudStack had a productive week across engineering, CI, documentation, and community maintenance. 🌟

Highlights

• Code and CI: Seven commits landed, including improved Sonar coverage-comment management, refreshed pre-commit hooks, and Copilot workflow token rotation.
• Documentation and discoverability: README status badges were expanded (good-first-issue, documentation, and website health), the star-history provider was repaired, and Markdown formatting was cleaned up.
• Pull requests: 30 recently updated PRs were surfaced: 28 remain open and 2 were closed. Active work spans configuration modernization, Ceph/RBD and storage, VMware/XCP-ng, console performance, OAuth APIs, autoscaling, networking, and UI fixes.
• Issue flow: Recently updated issues include a coordinated effort to phase out the deprecated Config enum (#10752, #13887, #13888, #13891, #13892, #13893), plus reports involving large-VM NAS backups (#13883), VMware datastore-cluster imports (#13885), the ISO upload UI (#13876), and duplicate usage records (#13399).
• Releases: No release was published during this reporting period. The latest release is CloudStack 4.22.1.0 LTS, published 2026-05-26.

Project status and recommendations

The project is moving well, with especially good attention to maintainability and contributor experience. The breadth of active storage, hypervisor, API, and console work is encouraging; prioritization and review bandwidth will be important as the queue grows.

1. Keep the Config enum migration coordinated, including compatibility, test refactoring, and configuration-type changes.
2. Prioritize review and validation for user-impacting storage/backup and VMware issues, particularly large-VM NAS backups and datastore-cluster imports.
3. Continue closing the loop on CI quality signals, coverage comments, and dependency/tooling updates.
4. Confirm documentation and upgrade guidance remain aligned with the 4.22 LTS maintenance line, and keep inviting contributions through the visible good-first-issue path.

Next steps for maintainers

• Triage newly reported operational and UI bugs, assigning owners and reproduction details where possible.
• Group related configuration-refactor issues and track them against a clear migration milestone.
• Review aging/high-discussion PRs and identify candidates for merge, revision, or closure.
• Maintain release-readiness focus for the next maintenance release, including regression coverage for storage, access control, and console changes.

Thanks to everyone contributing code, reviews, documentation, CI improvements, and project maintenance! 🚀

Generated by Weekly Repo Status · gpt56 190.1K · ◷

Add this agentic workflows to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-status.md@main