You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tooling.apache.org by "dave2wave (via GitHub)" <gi...@apache.org> on 2026/04/22 19:58:43 UTC
[I] During beta track (tooling-trusted-releases)
dave2wave opened a new issue, #1192:
URL: https://github.com/apache/tooling-trusted-releases/issues/1192
## Discussion
- [ ] #1033
- [ ] #1052
## Improvements
- [ ] #236
- [ ] #962
- [ ] #991
## ASVS
- [ ] #1021
- [ ] #1056
- [ ] #1062
- [ ] #1075
- [ ] #1112
## Paging
- [ ] #276
- [ ] #1072
## Operations
- [ ] #979
- [ ] #1049
- [ ] #1066
- [ ] #1067
- [ ] #1068
- [ ] #1069
- [ ] #1070
- [ ] #1132
- [ ] #1133
- [ ] #1149
--
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: dev-unsubscribe@tooling.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] During beta track (tooling-trusted-releases)
Posted by "asf-tooling (via GitHub)" <gi...@apache.org>.
asf-tooling commented on issue #1192:
URL: https://github.com/apache/tooling-trusted-releases/issues/1192#issuecomment-4409717618
<!-- gofannon-issue-triage-bot v2 -->
**Automated triage** — analyzed at `main@2da7807a`
**Type:** `discussion` • **Classification:** `no_action` • **Confidence:** `high`
**Application domain(s):** `release_lifecycle`
### Summary
This is a project management tracking issue (meta-issue) that aggregates multiple other issues into a checklist for the beta release phase. It references ~25 other issues across categories like Discussion, Approvals, Attestations, Improvements, Functional ASVS, Paging, and Operations ASVS. The issue itself does not request a specific code change — each referenced issue (#1033, #1052, #335, etc.) would have its own discrete implementation. Three items are already checked off (#1033, #236, #1069).
### Where this lives in the code today
#### `atr/get/finish.py` — `selected` (lines 60-70)
_currently does this_
Part of the release lifecycle (finish phase) that this tracking issue's domain encompasses, but no specific change is requested to this code by the issue itself.
```python
@get.typed
async def selected(
session: web.Committer,
_finish: Literal["finish"],
project_key: safe.ProjectKey,
version_key: safe.VersionKey,
) -> tuple[web.QuartResponse, int] | web.WerkzeugResponse | str:
"""
URL: /finish/<project_key>/<version_key>
Finish a release preview.
"""
```
#### `atr/get/compose.py` — `selected` (lines 47-57)
_currently does this_
Part of the release compose phase in the lifecycle; relevant to the beta track but no direct change requested.
```python
@get.typed
async def selected(
session: web.Committer,
_compose: Literal["compose"],
project_key: safe.ProjectKey,
version_key: safe.VersionKey,
) -> web.WerkzeugResponse | str:
"""
URL: /compose/<project_key>/<version_key>
Show the contents of the release candidate draft.
"""
```
#### `atr/get/release.py` — `releases` (lines 33-45)
_currently does this_
Public release listing page, part of the release lifecycle domain.
```python
@get.typed
async def releases(_session: web.Public, _releases: Literal["releases"]) -> str:
"""
URL: /releases
View all releases.
"""
# Releases are public, so we don't need to filter by user
async with db.session() as data:
releases = await data.release(
phase=sql.ReleasePhase.RELEASE,
_committee=True,
_project=True,
).all()
```
### Proposed approach
This issue is a tracking checklist and does not itself require any code changes. Each sub-issue referenced (e.g., #1052, #335, #1230, #326, #250, #214, #437, #1154, #962, #382, #1021, #1062, #1075, #1112, #276, #1072, #979, #1049, #1056, #1066, #1067, #1068, #1070, #1132, #1133, #1149) would need to be triaged individually to determine their specific code changes.
The appropriate action is to leave this issue open as a coordination artifact and address the individual referenced issues on their own merits.
### Open questions
- Each referenced sub-issue would need its own triage to determine specific code changes
- The priority ordering among the unchecked items is not clear from the issue body alone
- Whether any of the referenced issues are blocked on each other or have dependency ordering
_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
- `atr/get/finish.py`
- `atr/post/finish.py`
- `atr/shared/finish.py`
- `atr/get/compose.py`
- `atr/get/release.py`
- `atr/post/compose.py`
- `atr/post/draft.py`
- `atr/post/revisions.py`
### Related issues
This issue appears related to: #512.
_Both are tracking/punchlist issues for beta and alpha phases with multiple sub-tasks_
---
*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: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] During beta track (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave closed issue #1192: During beta track
URL: https://github.com/apache/tooling-trusted-releases/issues/1192
--
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: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org