dev  

Messages by Thread

• [I] Decide upon a platform name and hosts (tooling-trusted-release) via GitHub
  • Re: [I] Decide upon a platform name and hosts (tooling-trusted-release) via GitHub
• [I] Create a GitHub Action to make it easier to upload to the ATR (tooling-trusted-release) via GitHub
  • Re: [I] Create a GitHub Action to make it easier to upload to the ATR (tooling-trusted-release) via GitHub
  • Re: [I] Create a GitHub Action to make it easier to upload to the ATR (tooling-trusted-release) via GitHub
• [I] Obtain more information about permitting projects to upload from GitHub (tooling-trusted-release) via GitHub
  • Re: [I] Obtain more information about permitting projects to upload from GitHub (tooling-trusted-release) via GitHub
  • Re: [I] Obtain more information about permitting projects to upload from GitHub (tooling-trusted-release) via GitHub
  • Re: [I] Obtain more information about permitting projects to upload from GitHub (tooling-trusted-release) via GitHub
  • Re: [I] Obtain more information about permitting projects to upload from GitHub (tooling-trusted-release) via GitHub
• [I] Potentially allow upload from GHAs during the finish phase (tooling-trusted-release) via GitHub
  • Re: [I] Potentially allow upload from GHAs during the finish phase (tooling-trusted-release) via GitHub
  • Re: [I] Potentially allow upload from GHAs during the finish phase (tooling-trusted-release) via GitHub
  • Re: [I] Potentially allow upload from GHAs during the finish phase (tooling-trusted-release) via GitHub
• [I] Implement RAO / Maven connectivity (tooling-trusted-release) via GitHub
• [I] Add manual recording of packages released through external distribution channels (tooling-trusted-release) via GitHub
  • Re: [I] Add manual recording of packages released through external distribution channels (tooling-trusted-release) via GitHub
  • Re: [I] Add manual recording of packages released through external distribution channels (tooling-trusted-release) via GitHub
• [I] Add log sealing (tooling-trusted-release) via GitHub
• [I] Bug use of PAT and JWT is not registered on the manage tokens page (tooling-trusted-release) via GitHub
  • Re: [I] Bug use of PAT and JWT is not registered on the manage tokens page (tooling-trusted-release) via GitHub
  • Re: [I] Bug use of PAT and JWT is not registered on the manage tokens page (tooling-trusted-release) via GitHub
• [I] Hide upload keys on standing committee pages (tooling-trusted-release) via GitHub
  • Re: [I] Hide upload keys on standing committee pages (tooling-trusted-release) via GitHub
  • Re: [I] Hide upload keys on standing committee pages (tooling-trusted-release) via GitHub
• [I] Bug error when navigating to projects page (tooling-trusted-release) via GitHub
  • Re: [I] Bug error when navigating to projects page (tooling-trusted-release) via GitHub
  • Re: [I] Bug error when navigating to projects page (tooling-trusted-release) via GitHub
• [I] Bug projects are duplicated on committee page (tooling-trusted-release) via GitHub
  • Re: [I] Bug projects are duplicated on committee page (tooling-trusted-release) via GitHub
  • Re: [I] Bug projects are duplicated on committee page (tooling-trusted-release) via GitHub
• [I] Add tests suited to the alpha2 phase (tooling-trusted-release) via GitHub
• [I] Add developer documentation (tooling-trusted-release) via GitHub
• [I] Add/activate openapi endpoints (tooling-trusted-release) via GitHub
  • Re: [I] Add/activate openapi endpoints (tooling-trusted-release) via GitHub
  • Re: [I] Add/activate openapi endpoints (tooling-trusted-release) via GitHub
• [I] Policy page under Documentation (tooling-trusted-release) via GitHub
  • Re: [I] Policy page under Documentation (tooling-trusted-release) via GitHub
  • Re: [I] Policy page under Documentation (tooling-trusted-release) via GitHub
• [I] Bug - error viewing a committees page (tooling-trusted-release) via GitHub
  • Re: [I] Bug - error viewing a committees page (tooling-trusted-release) via GitHub
  • Re: [I] Bug - error viewing a committees page (tooling-trusted-release) via GitHub
• [I] Migrate remaining code to the storage interface (tooling-trusted-release) via GitHub
• [I] Make the API stable, and document the fact (tooling-trusted-release) via GitHub
• [PR] Clean up the Makefile and pre-commit config (tooling-docs) via GitHub
  • Re: [PR] Clean up the Makefile and pre-commit config (tooling-docs) via GitHub
• [I] Missing `favicon.ico` warnings when running `pelican -l` (tooling-docs) via GitHub
  • Re: [I] Missing `favicon.ico` warnings when running `pelican -l` (tooling-docs) via GitHub
  • Re: [I] Missing `favicon.ico` warnings when running `pelican -l` (tooling-docs) via GitHub
  • Re: [I] Missing `favicon.ico` warnings when running `pelican -l` (tooling-docs) via GitHub
• [PR] Expand the pre-commit config (tooling-trusted-release) via GitHub
  • Re: [PR] Expand the pre-commit config (tooling-trusted-release) via GitHub
  • Re: [PR] Expand the pre-commit config (tooling-trusted-release) via GitHub
• [I] We could add `zizmor` with `pre-commit`: static analysis for GitHub Actions (tooling-docs) via GitHub
• [PR] Add some docs on pre-commit (tooling-docs) via GitHub
  • Re: [PR] Add some docs on pre-commit (tooling-docs) via GitHub
  • Re: [PR] Add some docs on pre-commit (tooling-docs) via GitHub
• [I] The staging website is broken, with JS integrity errors (tooling-docs) via GitHub
  • Re: [I] The staging website is broken, with JS integrity errors (tooling-docs) via GitHub
  • Re: [I] The staging website is broken, with JS integrity errors (tooling-docs) via GitHub
  • Re: [I] The staging website is broken, with JS integrity errors (tooling-docs) via GitHub
  • Re: [I] The staging website is broken, with JS integrity errors (tooling-docs) via GitHub
  • Re: [I] The staging website is broken, with JS integrity errors (tooling-docs) via GitHub
  • Re: [I] The staging website is broken, with JS integrity errors (tooling-docs) via GitHub
  • Re: [I] The staging website is broken, with JS integrity errors (tooling-docs) via GitHub
  • Re: [I] The staging website is broken, with JS integrity errors (tooling-docs) via GitHub
  • Re: [I] The staging website is broken, with JS integrity errors (tooling-docs) via GitHub
• [PR] pre-commit: add markdownlint and fix Markdown linter errors (tooling-docs) via GitHub
  • Re: [PR] pre-commit: add markdownlint and fix Markdown linter errors (tooling-docs) via GitHub
• [PR] Create Makefile for more automation and convenience (tooling-docs) via GitHub
  • Re: [PR] Create Makefile for more automation and convenience (tooling-docs) via GitHub
• [PR] Create two requirements files for `dev` and `docs` (tooling-docs) via GitHub
  • Re: [PR] Create two requirements files for `dev` and `docs` (tooling-docs) via GitHub
  • Re: [PR] Create two requirements files for `dev` and `docs` (tooling-docs) via GitHub
• [PR] pre-commit add spelling checking with crate `typos` (tooling-docs) via GitHub
  • Re: [PR] pre-commit add spelling checking with crate `typos` (tooling-docs) via GitHub
• [PR] pre-commit add yamllint (tooling-docs) via GitHub
  • Re: [PR] pre-commit add yamllint (tooling-docs) via GitHub
• [I] Add pre-commit hook `shellcheck-py` to standardize shell files (tooling-docs) via GitHub
  • Re: [I] Add pre-commit hook `shellcheck-py` to standardize shell files (tooling-docs) via GitHub
  • Re: [I] Add pre-commit hook `shellcheck-py` to standardize shell files (tooling-docs) via GitHub
  • Re: [I] Add pre-commit hook `shellcheck-py` to standardize shell files (tooling-docs) via GitHub
• [I] Add `pre-commit` hook `yamllint` to standardize YAML files (tooling-docs) via GitHub
  • Re: [I] Add `pre-commit` hook `yamllint` to standardize YAML files (tooling-docs) via GitHub
  • Re: [I] Add `pre-commit` hook `yamllint` to standardize YAML files (tooling-docs) via GitHub
• [I] Add `.gitattributes` configuration file (tooling-docs) via GitHub
  • Re: [I] Add `.gitattributes` configuration file (tooling-docs) via GitHub
  • Re: [I] Add `.gitattributes` configuration file (tooling-docs) via GitHub
• [I] Add `actionlint` with `pre-commit`: a static checker for GitHub Actions workflow files (tooling-docs) via GitHub
  • Re: [I] Add `actionlint` with `pre-commit`: a static checker for GitHub Actions workflow files (tooling-docs) via GitHub
• [I] Add `EditorConfig` it is `awesome` 🦸 🖥️ (tooling-docs) via GitHub
  • Re: [I] Add `EditorConfig` it is `awesome` 🦸 🖥️ (tooling-docs) via GitHub
• [I] pre-commit: add `markdown-link-check` to check for dead links in Markdown files (tooling-docs) via GitHub
  • Re: [I] pre-commit: add `markdown-link-check` to check for dead links in Markdown files (tooling-docs) via GitHub
  • Re: [I] pre-commit: add `markdown-link-check` to check for dead links in Markdown files (tooling-docs) via GitHub
• [I] pre-commit: add `markdownlint` and standardize Markdown files (tooling-docs) via GitHub
  • Re: [I] pre-commit: add `markdownlint` and standardize Markdown files (tooling-docs) via GitHub
  • Re: [I] pre-commit: add `markdownlint` and standardize Markdown files (tooling-docs) via GitHub
• [PR] README.md: order the Slack Channel list alphabetically (tooling-docs) via GitHub
  • Re: [PR] README.md: order the Slack Channel list alphabetically (tooling-docs) via GitHub
• [PR] gha: add pre-commit with about 15 hooks (tooling-docs) via GitHub
  • Re: [PR] gha: add pre-commit with about 15 hooks (tooling-docs) via GitHub
• [PR] Create Apache LICENSE (tooling-docs) via GitHub
  • Re: [PR] Create Apache LICENSE (tooling-docs) via GitHub
  • Re: [PR] Create Apache LICENSE (tooling-docs) via GitHub
• [I] Should we add an Apache License to this repo ? (tooling-docs) via GitHub
  • Re: [I] Should we add an Apache License to this repo ? (tooling-docs) via GitHub
  • Re: [I] Should we add an Apache License to this repo ? (tooling-docs) via GitHub
• [PR] Fix link and fix indent (tooling-docs) via GitHub
  • Re: [PR] Fix link and fix indent (tooling-docs) via GitHub
• [PR] misc: remove unneeded trailing whitespace (tooling-docs) via GitHub
  • Re: [PR] misc: remove unneeded trailing whitespace (tooling-docs) via GitHub
• [PR] Add missing Python package requirement `Markdown` (tooling-docs) via GitHub
  • Re: [PR] Add missing Python package requirement `Markdown` (tooling-docs) via GitHub
  • Re: [PR] Add missing Python package requirement `Markdown` (tooling-docs) via GitHub
  • Re: [PR] Add missing Python package requirement `Markdown` (tooling-docs) via GitHub
  • Re: [PR] Add missing Python package requirement `Markdown` (tooling-docs) via GitHub
• [PR] docs: fix link, spelling and whitespace (tooling-docs) via GitHub
  • [GH] docs: fix link, spelling and whitespace (tooling-docs) via GitHub
  • [GH] docs: fix link, spelling and whitespace (tooling-docs) via GitHub
  • Re: [PR] docs: spelling and whitespace (tooling-docs) via GitHub
  • Re: [PR] docs: spelling and whitespace (tooling-docs) via GitHub
• [PR] README: order the infrastructure links (tooling-docs) via GitHub
  • Re: [PR] README: order the infrastructure links (tooling-docs) via GitHub
• [PR] Order the packages alphabetically in `requirements.txt` (tooling-docs) via GitHub
  • Re: [PR] Order the packages alphabetically in `requirements.txt` (tooling-docs) via GitHub
  • Re: [PR] Order the packages alphabetically in `requirements.txt` (tooling-docs) via GitHub
• [PR] docs(apache-trusted-release): fix typos in Markdown files (tooling-docs) via GitHub
  • Re: [PR] docs(apache-trusted-release): fix typos in Markdown files (tooling-docs) via GitHub
  • Re: [PR] docs(apache-trusted-release): fix typos in Markdown files (tooling-docs) via GitHub
• Re: [I] Automation via GitHub Actions (tooling-trusted-release) via GitHub
  • Re: [I] Automation via GitHub Actions (tooling-trusted-release) via GitHub
  • Re: [I] Automation via GitHub Actions (tooling-trusted-release) via GitHub
  • Re: [I] Automation via GitHub Actions (tooling-trusted-release) via GitHub
  • Re: [I] Automation via GitHub Actions (tooling-trusted-release) via GitHub
  • Re: [I] Automation via GitHub Actions (tooling-trusted-release) via GitHub
  • Re: [I] Automation via GitHub Actions (tooling-trusted-release) via GitHub
  • Re: [I] Automation via GitHub Actions (tooling-trusted-release) via GitHub
• [I] Tie ATR server into the rsync path of svn dist artifacts (tooling-trusted-release) via GitHub
• [I] Beta1 Work (tooling-trusted-release) via GitHub
  • Re: [I] ATR Beta 1 Work (tooling-trusted-release) via GitHub
• [I] License header exceptions allowed in checks (tooling-trusted-release) via GitHub
  • Re: [I] License header exceptions allowed in checks (tooling-trusted-release) via GitHub
  • Re: [I] License header exceptions allowed in checks (tooling-trusted-release) via GitHub
  • Re: [I] License header exceptions allowed in checks (tooling-trusted-release) via GitHub
  • Re: [I] License header exceptions allowed in checks (tooling-trusted-release) via GitHub
• [PR] Update lifecycle.md (tooling-docs) via GitHub
  • Re: [PR] Update lifecycle.md (tooling-docs) via GitHub
• [I] Second round vote email fails to send (tooling-trusted-release) via GitHub
  • Re: [I] Second round vote email fails to send (tooling-trusted-release) via GitHub
  • Re: [I] Second round vote email fails to send (tooling-trusted-release) via GitHub
• [I] Vote form should distinguish between binding votes and non-binding according to the user (tooling-trusted-release) via GitHub
  • Re: [I] Vote form should distinguish between binding votes and non-binding according to the user (tooling-trusted-release) via GitHub
  • Re: [I] Vote form should distinguish between binding votes and non-binding according to the user (tooling-trusted-release) via GitHub
  • Re: [I] Vote form should distinguish between binding votes and non-binding according to the user (tooling-trusted-release) via GitHub
• [I] Create an API for read-only data, and existing ATR workflows (tooling-trusted-release) via GitHub
  • Re: [I] Create an API for read-only data, and existing ATR workflows (tooling-trusted-release) via GitHub
  • Re: [I] Create an API for read-only data, and existing ATR workflows (tooling-trusted-release) via GitHub
  • Re: [I] Create an API for read-only data, and existing ATR workflows (tooling-trusted-release) via GitHub
  • Re: [I] Create an API for read-only data, and existing ATR workflows (tooling-trusted-release) via GitHub
• [I] Show link to the Vote thread on resolve page (tooling-trusted-release) via GitHub
  • Re: [I] Show link to the Vote thread on resolve page (tooling-trusted-release) via GitHub
  • Re: [I] Show link to the Vote thread on resolve page (tooling-trusted-release) via GitHub
• Re: [I] Recording and Reporting of Release Votes (tooling-trusted-release) via GitHub
  • Re: [I] Recording and Reporting of Release Votes (tooling-trusted-release) via GitHub
• [I] Use stagex for the default container (tooling-trusted-release) via GitHub
• [I] Releases for an incubator podling belong in subfolders of `incubator` (tooling-trusted-release) via GitHub
• [I] Finish - add a select all on the file move (tooling-trusted-release) via GitHub
• [I] Add further validation to check site consistency (tooling-trusted-release) via GitHub
• [I] Release Vote Stage (tooling-trusted-release) via GitHub
  • Re: [I] Release Vote Stage (tooling-trusted-release) via GitHub
• [I] Allow extra RAT excludes to be specified in the ATR interface (tooling-trusted-release) via GitHub
  • Re: [I] Allow extra RAT excludes to be specified in the ATR interface (tooling-trusted-release) via GitHub
  • Re: [I] Allow extra RAT excludes to be specified in the ATR interface (tooling-trusted-release) via GitHub
  • Re: [I] Allow extra RAT excludes to be specified in the ATR interface (tooling-trusted-release) via GitHub
• [I] Selecting "Manual voting process" should hide the rest of the vote section (tooling-trusted-release) via GitHub
  • Re: [I] Selecting "Manual voting process" should hide the rest of the vote section (tooling-trusted-release) via GitHub
  • Re: [I] Selecting "Manual voting process" should hide the rest of the vote section (tooling-trusted-release) via GitHub
  • Re: [I] Selecting "Manual voting process" should hide the rest of the vote section (tooling-trusted-release) via GitHub
• [I] Projects page divide the Release Policy section into three sections (tooling-trusted-release) via GitHub
  • Re: [I] Projects page divide the Release Policy section into three sections (tooling-trusted-release) via GitHub
  • Re: [I] Projects page divide the Release Policy section into three sections (tooling-trusted-release) via GitHub
• [I] Add a strict compliance checkbox to the project release policy form (tooling-trusted-release) via GitHub
  • Re: [I] Add a strict compliance checkbox to the project release policy form (tooling-trusted-release) via GitHub
  • Re: [I] Add a strict compliance checkbox to the project release policy form (tooling-trusted-release) via GitHub
• [I] Provide an api (tooling-trusted-release) via GitHub
• [I] Release Artifact Database (tooling-trusted-release) via GitHub
• [I] Update catalog during ATR releases (tooling-trusted-release) via GitHub
• [I] Committee archive catalog (tooling-trusted-release) via GitHub
• [PR] Bump urllib3 from 2.4.0 to 2.5.0 (tooling-trusted-release) via GitHub
  • Re: [PR] Bump urllib3 from 2.4.0 to 2.5.0 (tooling-trusted-release) via GitHub
  • Re: [PR] Bump urllib3 from 2.4.0 to 2.5.0 (tooling-trusted-release) via GitHub
  • Re: [PR] Bump urllib3 from 2.4.0 to 2.5.0 (tooling-trusted-release) via GitHub
• [I] Do not allow keys to be deleted if they have been used to sign a release (tooling-trusted-release) via GitHub
  • Re: [I] Do not allow keys to be deleted if they have been used to sign a release (tooling-trusted-release) via GitHub
  • Re: [I] Do not allow keys to be deleted if they have been used to sign a release (tooling-trusted-release) via GitHub
  • Re: [I] Do not allow keys to be deleted if they have been used to sign a release (tooling-trusted-release) via GitHub
  • Re: [I] Do not allow keys to be deleted if they have been used to sign a release (tooling-trusted-release) via GitHub
  • Re: [I] Do not allow keys to be deleted if they have been used to sign a release (tooling-trusted-release) via GitHub
  • Re: [I] Do not allow keys to be deleted if they have been used to sign a release (tooling-trusted-release) via GitHub

• Earlier messages