issues  

Messages by Thread

• • Re: [PR] Adjust downloads menu target (tooling-trusted-releases) via GitHub
  • Re: [PR] Adjust downloads menu target (tooling-trusted-releases) via GitHub
  • Re: [PR] Adjust downloads menu target (tooling-trusted-releases) via GitHub
• [I] Remove the downloads area feature (tooling-trusted-releases) via GitHub
  • Re: [I] Remove the downloads area feature (tooling-trusted-releases) via GitHub
  • Re: [I] Remove the downloads area feature (tooling-trusted-releases) via GitHub
  • Re: [I] Remove the downloads area feature (tooling-trusted-releases) via GitHub
  • Re: [I] Remove the downloads area feature (tooling-trusted-releases) via GitHub
  • Re: [I] Remove the downloads area feature (tooling-trusted-releases) via GitHub
  • Re: [I] Remove the downloads area feature (tooling-trusted-releases) via GitHub
  • Re: [I] Remove the downloads area feature (tooling-trusted-releases) via GitHub
  • Re: [I] Remove the downloads area feature (tooling-trusted-releases) via GitHub
  • Re: [I] Remove the downloads area feature (tooling-trusted-releases) via GitHub
  • Re: [I] Remove the downloads area feature (tooling-trusted-releases) via GitHub
• [I] Do not allow arbitrary committers to publish to SVN (tooling-trusted-releases) via GitHub
  • Re: [I] Do not allow arbitrary committers to publish to SVN (tooling-trusted-releases) via GitHub
  • Re: [I] Do not allow arbitrary committers to publish to SVN (tooling-trusted-releases) via GitHub
  • Re: [I] Do not allow arbitrary committers to publish to SVN (tooling-trusted-releases) via GitHub
  • Re: [I] Do not allow arbitrary committers to publish to SVN (tooling-trusted-releases) via GitHub
• Re: [I] Build ATR production server (tooling-trusted-releases) via GitHub
  • Re: [I] Build ATR production server (tooling-trusted-releases) via GitHub
• [I] Fix the embargoed release wording (tooling-trusted-releases) via GitHub
  • Re: [I] Fix the embargoed release wording (tooling-trusted-releases) via GitHub
  • Re: [I] Fix the embargoed release wording (tooling-trusted-releases) via GitHub
  • Re: [I] Fix the embargoed release wording (tooling-trusted-releases) via GitHub
• [I] Add management options for KEYS files, and remove regenerate all (tooling-trusted-releases) via GitHub
  • Re: [I] Add management options for KEYS files, and remove regenerate all (tooling-trusted-releases) via GitHub
  • Re: [I] Add management options for KEYS files, and remove regenerate all (tooling-trusted-releases) via GitHub
• [I] Signing SBOMs (tooling-trusted-releases) via GitHub
  • Re: [I] Signing SBOMs (tooling-trusted-releases) via GitHub
  • Re: [I] Signing SBOMs (tooling-trusted-releases) via GitHub
  • Re: [I] Signing SBOMs (tooling-trusted-releases) via GitHub
  • Re: [I] Signing SBOMs (tooling-trusted-releases) via GitHub
  • Re: [I] Signing SBOMs (tooling-trusted-releases) via GitHub
• Re: [I] Integrate ATR secrets with Puppet (tooling-trusted-releases) via GitHub
  • Re: [I] Integrate ATR secrets with Puppet (tooling-trusted-releases) via GitHub
• [I] Move SVN_DIST_PUBLIC_URL to the configuration (tooling-trusted-releases) via GitHub
  • Re: [I] Move SVN_DIST_PUBLIC_URL to the configuration (tooling-trusted-releases) via GitHub
  • Re: [I] Move SVN_DIST_PUBLIC_URL to the configuration (tooling-trusted-releases) via GitHub
• Re: [I] Setup svn credentials to commit to dist/release (tooling-trusted-releases) via GitHub
  • Re: [I] Setup svn credentials to commit to dist/release (tooling-trusted-releases) via GitHub
  • Re: [I] Setup svn credentials to commit to dist/release (tooling-trusted-releases) via GitHub
• Re: [I] Missing Centralized Documentation of Resource-Intensive Operations (tooling-trusted-releases) via GitHub
  • Re: [I] Missing Centralized Documentation of Resource-Intensive Operations (tooling-trusted-releases) via GitHub
  • Re: [I] Missing Centralized Documentation of Resource-Intensive Operations (tooling-trusted-releases) via GitHub
• [I] Update the tutorial (tooling-trusted-releases) via GitHub
• [I] Document SBOM workflow for users (tooling-trusted-releases) via GitHub
• [PR] Bump soupsieve from 2.8 to 2.8.4 (tooling-docs) via GitHub
  • Re: [PR] Bump soupsieve from 2.8 to 2.8.4 (tooling-docs) via GitHub
• Re: [PR] Add SBOM workflows documentation (tooling-trusted-releases) via GitHub
• [I] Files not found for release with multiple directory (tooling-trusted-releases) via GitHub
  • Re: [I] Files not found for release with multiple directory (tooling-trusted-releases) via GitHub
  • Re: [I] Files not found for release with multiple directory (tooling-trusted-releases) via GitHub
  • Re: [I] Files not found for release with multiple directory (tooling-trusted-releases) via GitHub
• Re: [PR] [INFRA] Set up default rulesets for default and release branches (tooling-releases-client) via GitHub
• [I] Revisit build attestations and SLSA (tooling-trusted-releases) via GitHub
• [I] Document SLSA attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Document SLSA attestations (tooling-trusted-releases) via GitHub
• [I] Document reproducible builds and permission to use CI (tooling-trusted-releases) via GitHub
  • Re: [I] Document reproducible builds and permission to use CI (tooling-trusted-releases) via GitHub
• Re: [I] Document reproducible builds, signing, SBOMs, and OpenSSF (tooling-trusted-releases) via GitHub
  • Re: [I] Document reproducible builds, signing, SBOMs, and OpenSSF (tooling-trusted-releases) via GitHub
• Re: [I] Document the scope of ATR (tooling-trusted-releases) via GitHub
  • Re: [I] Document the scope of ATR (tooling-trusted-releases) via GitHub
• [I] add MAJOR_VERSION variable to Default download path suffix (tooling-trusted-releases) via GitHub
  • Re: [I] add MAJOR_VERSION variable to Default download path suffix (tooling-trusted-releases) via GitHub
  • Re: [I] add MAJOR_VERSION variable to Default download path suffix (tooling-trusted-releases) via GitHub
  • Re: [I] add MAJOR_VERSION variable to Default download path suffix (tooling-trusted-releases) via GitHub
• [I] Security concern about stack-traces (tooling-releases-client) via GitHub
  • Re: [I] Security concern about stack-traces (tooling-releases-client) via GitHub
  • Re: [I] Security concern about stack-traces (tooling-releases-client) via GitHub
  • Re: [I] Security concern about stack-traces (tooling-releases-client) via GitHub
  • Re: [I] Security concern about stack-traces (tooling-releases-client) via GitHub
  • Re: [I] Security (defense-in-depth) concern about stack-traces (tooling-releases-client) via GitHub
  • Re: [I] Security (defense-in-depth) concern about stack-traces (tooling-releases-client) via GitHub
• [I] Error 500 when trying to use `atr vote start' (tooling-releases-client) via GitHub
  • Re: [I] Error 500 when trying to use `atr vote start' (tooling-releases-client) via GitHub
  • Re: [I] Error 500 when trying to use `atr vote start' (tooling-releases-client) via GitHub
  • Re: [I] Error 500 when trying to use `atr vote start' (tooling-releases-client) via GitHub
  • Re: [I] Error 500 when trying to use `atr vote start' (tooling-releases-client) via GitHub
  • Re: [I] Error 500 when trying to use `atr vote start' (tooling-releases-client) via GitHub
• [I] Specifying revision is harmful/not needed (tooling-releases-client) via GitHub
  • Re: [I] Specifying revision is harmful/not needed (tooling-releases-client) via GitHub
  • Re: [I] Specifying revision is harmful/not needed (tooling-releases-client) via GitHub
  • Re: [I] Specifying revision is harmful/not needed (tooling-releases-client) via GitHub
  • Re: [I] Specifying revision is harmful/not needed (tooling-releases-client) via GitHub
  • Re: [I] Specifying revision is harmful/not needed (tooling-releases-client) via GitHub
  • Re: [I] Specifying revision is harmful/not needed (tooling-releases-client) via GitHub
  • Re: [I] Specifying revision is harmful/not needed (tooling-releases-client) via GitHub
• [I] No obvious way how to resolve concerns (tooling-releases-client) via GitHub
  • Re: [I] No obvious way how to resolve concerns (tooling-releases-client) via GitHub
  • Re: [I] No obvious way how to resolve concerns (tooling-releases-client) via GitHub
  • Re: [I] No obvious way how to resolve concerns (tooling-releases-client) via GitHub
  • Re: [I] No obvious way how to resolve concerns (tooling-releases-client) via GitHub
• [I] The atr client returns json response by default rather than human readable messages (tooling-releases-client) via GitHub
  • Re: [I] The atr client returns json response by default rather than human readable messages (tooling-releases-client) via GitHub
  • Re: [I] The atr client returns json response by default rather than human readable messages (tooling-releases-client) via GitHub
  • Re: [I] The atr client returns json response by default rather than human readable messages (tooling-releases-client) via GitHub
  • Re: [I] The atr client returns json response by default rather than human readable messages (tooling-releases-client) via GitHub
  • Re: [I] The atr client returns json response by default rather than human readable messages (tooling-releases-client) via GitHub
  • Re: [I] The atr client returns json response by default rather than human readable messages (tooling-releases-client) via GitHub
  • Re: [I] The atr client returns json response by default rather than human readable messages (tooling-releases-client) via GitHub
• [I] Empty __init__.py and similar files are recognized as missing licences (tooling-trusted-releases) via GitHub
  • Re: [I] Empty __init__.py and similar files are recognized as missing licences (tooling-trusted-releases) via GitHub
  • Re: [I] Empty __init__.py and similar files are recognized as missing licences (tooling-trusted-releases) via GitHub
  • Re: [I] Empty __init__.py and similar files are recognized as missing licences (tooling-trusted-releases) via GitHub
  • Re: [I] Empty __init__.py and similar files are recognized as missing licences (tooling-trusted-releases) via GitHub
• [I] SPDX licences are not recognized properly by ATR (tooling-trusted-releases) via GitHub
  • Re: [I] SPDX licences are not recognized properly by ATR (tooling-trusted-releases) via GitHub
  • Re: [I] SPDX licences are not recognized properly by ATR (tooling-trusted-releases) via GitHub
  • Re: [I] SPDX licences are not recognized properly by ATR (tooling-trusted-releases) via GitHub
  • Re: [I] SPDX licences are not recognized properly by ATR (tooling-trusted-releases) via GitHub
  • Re: [I] SPDX licences are not recognized properly by ATR (tooling-trusted-releases) via GitHub
  • Re: [I] SPDX licences are not recognized properly by ATR (tooling-trusted-releases) via GitHub
  • Re: [I] SPDX licences are not recognized properly by ATR (tooling-trusted-releases) via GitHub
  • Re: [I] SPDX licences are not recognized properly by ATR (tooling-trusted-releases) via GitHub
• [I] Use pill buttons instead of links on catalog artifact UI (tooling-trusted-releases) via GitHub
  • Re: [I] Use pill buttons instead of links on catalog artifact UI (tooling-trusted-releases) via GitHub
  • Re: [I] Use pill buttons instead of links on catalog artifact UI (tooling-trusted-releases) via GitHub
• [I] The atr client does not allow to set PAT token from stdin (tooling-releases-client) via GitHub
  • Re: [I] The atr client does not allow to set PAT token from stdin (tooling-releases-client) via GitHub
  • Re: [I] The atr client does not allow to set PAT token from stdin (tooling-releases-client) via GitHub
  • Re: [I] The atr client does not allow to set PAT token from stdin (tooling-releases-client) via GitHub
  • Re: [I] The atr client does not allow to set PAT token from stdin (tooling-releases-client) via GitHub
  • Re: [I] The atr client does not allow to set PAT token from stdin (tooling-releases-client) via GitHub
  • Re: [I] The atr client does not allow to set PAT token from stdin (tooling-releases-client) via GitHub
• [PR] Update components (tooling-trusted-releases) via GitHub
  • Re: [PR] Update components (tooling-trusted-releases) via GitHub
• [PR] #1370 - support import and export of PMC CSVs (tooling-trusted-releases) via GitHub
  • [GH] #1370 - support import and export of PMC CSVs (tooling-trusted-releases) via GitHub
  • [GH] #1370 - support import and export of PMC CSVs (tooling-trusted-releases) via GitHub
  • [GH] #1370 - support import and export of PMC CSVs (tooling-trusted-releases) via GitHub
  • [GH] #1370 - support import and export of PMC CSVs (tooling-trusted-releases) via GitHub
  • [GH] #1370 - support import and export of PMC CSVs (tooling-trusted-releases) via GitHub
  • [GH] #1370 - support import and export of PMC CSVs (tooling-trusted-releases) via GitHub
  • [GH] #1370 - support import and export of PMC CSVs (tooling-trusted-releases) via GitHub
  • [GH] #1370 - support import and export of PMC CSVs (tooling-trusted-releases) via GitHub
  • [GH] #1370 - support import and export of PMC CSVs (tooling-trusted-releases) via GitHub
  • Re: [PR] #1370 - support import and export of PMC CSVs (tooling-trusted-releases) via GitHub
  • [GH] #1370 - support import and export of PMC CSVs (tooling-trusted-releases) via GitHub
  • [GH] #1370 - support import and export of PMC CSVs (tooling-trusted-releases) via GitHub
  • [GH] #1370 - support import and export of PMC CSVs (tooling-trusted-releases) via GitHub
  • [GH] #1370 - support import and export of PMC CSVs (tooling-trusted-releases) via GitHub
  • [GH] #1370 - support import and export of PMC CSVs (tooling-trusted-releases) via GitHub
  • Re: [PR] #1370 - support import and export of PMC CSVs (tooling-trusted-releases) via GitHub
  • Re: [PR] #1370 - support import and export of PMC CSVs (tooling-trusted-releases) via GitHub
• [PR] Bump actions/setup-java from 5.3.0 to 5.5.0 [tooling-atr-maven-plugin] via GitHub
  • Re: [PR] Bump actions/setup-java from 5.3.0 to 5.5.0 [tooling-atr-maven-plugin] via GitHub
• [I] Make banner message configurable by environment (tooling-trusted-releases) via GitHub
  • Re: [I] Make banner message configurable by environment (tooling-trusted-releases) via GitHub
  • Re: [I] Make banner message configurable by environment (tooling-trusted-releases) via GitHub
  • Re: [I] Make banner message configurable by environment (tooling-trusted-releases) via GitHub
  • Re: [I] Make banner message configurable by environment (tooling-trusted-releases) via GitHub
• [I] Beta documentation updates (tooling-trusted-releases) via GitHub
• Re: [I] Document ATR disk layout and size requirements (tooling-trusted-releases) via GitHub
  • Re: [I] Document ATR disk layout and size requirements (tooling-trusted-releases) via GitHub
  • Re: [I] Document ATR disk layout and size requirements (tooling-trusted-releases) via GitHub
  • Re: [I] Document ATR disk layout and size requirements (tooling-trusted-releases) via GitHub
  • Re: [I] Document ATR disk layout and size requirements (tooling-trusted-releases) via GitHub
  • Re: [I] Document ATR disk layout and size requirements (tooling-trusted-releases) via GitHub
  • Re: [I] Document ATR disk layout and size requirements (tooling-trusted-releases) via GitHub
• [I] Order of tiles on Releases page (tooling-trusted-releases) via GitHub
  • Re: [I] Order of tiles on Releases page (tooling-trusted-releases) via GitHub
• Re: [I] Committee release catalog schema and model complete (tooling-trusted-releases) via GitHub
• [I] Apply project and artifact catalog seeds (tooling-trusted-releases) via GitHub
• [I] Release archival actions (tooling-trusted-releases) via GitHub
  • Re: [I] Release archival actions (tooling-trusted-releases) via GitHub
  • Re: [I] Release archival actions (tooling-trusted-releases) via GitHub
• Re: [I] Add committee permissions (tooling-trusted-releases) via GitHub
  • Re: [I] Add committee permissions (tooling-trusted-releases) via GitHub
• [I] Admin page for seeding Projects and Artifact Catalog (tooling-trusted-releases) via GitHub
  • Re: [I] Admin page for seeding Projects and Artifact Catalog (tooling-trusted-releases) via GitHub
• Re: [I] Ensure that a release can only be deleted or archived, and that the state is clear (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that a release can only be deleted or archived, and that the state is clear (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that a release can only be deleted or archived, and that the state is clear (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that a release can only be deleted or archived, and that the state is clear (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that a release can only be deleted or archived, and that the state is clear (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that a release can only be deleted or archived, and that the state is clear (tooling-trusted-releases) via GitHub
• Re: [PR] Bump actions/cache from 5.0.4 to 5.0.5 (tooling-actions) via GitHub
  • Re: [PR] Bump actions/cache from 5.0.4 to 5.0.5 (tooling-actions) via GitHub
• [PR] Bump actions/cache from 5.0.4 to 6.1.0 (tooling-actions) via GitHub
  • Re: [PR] Bump actions/cache from 5.0.4 to 6.1.0 (tooling-actions) via GitHub
• [PR] Bump actions/setup-java from 5.3.0 to 5.4.0 (tooling-actions) via GitHub
  • Re: [PR] Bump actions/setup-java from 5.3.0 to 5.4.0 (tooling-actions) via GitHub
• [PR] Bump actions/setup-python from 6.2.0 to 6.3.0 (tooling-actions) via GitHub
  • Re: [PR] Bump actions/setup-python from 6.2.0 to 6.3.0 (tooling-actions) via GitHub
• [PR] Bump actions/cache from 5.0.5 to 6.1.0 (tooling-releases-client) via GitHub
  • Re: [PR] Bump actions/cache from 5.0.5 to 6.1.0 (tooling-releases-client) via GitHub
• [PR] Bump actions/setup-python from 6.2.0 to 6.3.0 (tooling-releases-client) via GitHub
  • Re: [PR] Bump actions/setup-python from 6.2.0 to 6.3.0 (tooling-releases-client) via GitHub
• Re: [I] Alpha3 Track (tooling-trusted-releases) via GitHub
• [I] Several committee guards are missing (tooling-trusted-releases) via GitHub
  • Re: [I] Several committee guards are missing (tooling-trusted-releases) via GitHub
  • Re: [I] Several committee guards are missing (tooling-trusted-releases) via GitHub
• [I] pending→confirmed transition discards upload_date/api_url/web_url (tooling-trusted-releases) via GitHub
• [I] Irreversible filesystem move + prior-revision deletion happen before the DB promotion CAS (tooling-trusted-releases) via GitHub
  • Re: [I] Irreversible filesystem move + prior-revision deletion happen before the DB promotion CAS (tooling-trusted-releases) via GitHub
  • Re: [I] Irreversible filesystem move + prior-revision deletion happen before the DB promotion CAS (tooling-trusted-releases) via GitHub
  • Re: [I] Irreversible filesystem move + prior-revision deletion happen before the DB promotion CAS (tooling-trusted-releases) via GitHub
• [I] validate_distribution_ssh_register targets a class missing from the Results union, so it always fails (tooling-trusted-releases) via GitHub

• Earlier messages
• Later messages