asf-tooling commented on issue #450: URL: https://github.com/apache/tooling-trusted-releases/issues/450#issuecomment-4410292558
<!-- gofannon-issue-triage-bot v2 --> **Automated triage** — analyzed at `main@2da7807a` **Type:** `discussion` • **Classification:** `no_action` • **Confidence:** `high` **Application domain(s):** `project_committee_management`, `release_lifecycle`, `shared_infrastructure` ### Summary This is a planning/tracking issue that enumerates features from the comdev reporter.apache.org platform and categorizes them into three migration targets: (1) Board Agenda Tool, (2) Infra's catalog effort, and (3) ATR (this repository). The ATR-relevant items identified are `scandist.py` (release monitoring daemon), `addrelease.html` (release entry UI), and release lists/sub-projects. No concrete code change is proposed — it's a checklist for future migration decisions. No prior discussion exists on this issue. ### Proposed approach This issue is an open-ended planning document. The ATR-relevant features it identifies (release monitoring/notification similar to `scandist.py`, release entry workflows similar to `addrelease.html`) would likely be implemented in the existing release lifecycle subsystem (e.g., `atr/storage/writers/release.py`, `atr/get/compose.py`) and potentially as new background tasks (in `atr/tasks/`). However, no specific implementation is being requested — the issue is tracking what should eventually be migrated. No code changes should be proposed at this stage. The issue serves as a discussion anchor for deciding ownership of features across multiple ASF platforms. The team needs to determine which specific reporter features will be absorbed by ATR and create individual implementation issues from those decisions. ### Open questions - Which specific features from the reporter checklist have already been implemented in ATR (e.g., release monitoring may overlap with existing vote/finish workflows)? - Is the 'catalog effort' mentioned in the issue tracked elsewhere, and does ATR need to integrate with it for committee data? - Should `scandist.py` functionality (watching dist for releases and prompting entry) be a new ATR task, or is it already covered by the existing release lifecycle? - Has there been any off-GitHub discussion (mailing list, etc.) about the migration priorities for this issue? _The agent reviewed this issue and is not proposing patches in this run. Review the existing-code citations and open questions above before deciding next steps._ ### Files examined - `.asf.yaml` - `.github/PULL_REQUEST_TEMPLATE.md` - `.github/dependabot.yml` - `.github/labeler.yml` - `.github/linters/.markdown-lint.yml` - `.github/workflows/allowlistchecker.yml` - `.github/workflows/analyze.yml` - `.github/workflows/build.yml` --- *Draft from a triage agent. A human reviewer should validate before merging any change. The agent did not run tests or verify diffs apply.* -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
