dev  

Messages by Thread

• • Re: [I] Document the version identification system in ATR where a release is started (tooling-trusted-releases) via GitHub
  • Re: [I] Document the version identification system in ATR where a release is started (tooling-trusted-releases) via GitHub
  • Re: [I] Document the version identification system in ATR where a release is started (tooling-trusted-releases) via GitHub
• [I] Retry failed email deliveries (tooling-trusted-releases) via GitHub
  • Re: [I] Retry failed email deliveries (tooling-trusted-releases) via GitHub
  • Re: [I] Retry failed email deliveries (tooling-trusted-releases) via GitHub
• Fail to submit report for iotdb and tsfile through the online Board Agenda Tool Yuan Tian
  • Re: Fail to submit report for iotdb and tsfile through the online Board Agenda Tool sebb
  • Re: Fail to submit report for iotdb and tsfile through the online Board Agenda Tool sebb
  • Re: Fail to submit report for iotdb and tsfile through the online Board Agenda Tool Yuan Tian
  • Re: Fail to submit report for iotdb and tsfile through the online Board Agenda Tool sebb
  • Re: Fail to submit report for iotdb and tsfile through the online Board Agenda Tool Yuan Tian
  • Re: Fail to submit report for iotdb and tsfile through the online Board Agenda Tool Dave Fisher
  • Re: Fail to submit report for iotdb and tsfile through the online Board Agenda Tool sebb
  • Re: Fail to submit report for iotdb and tsfile through the online Board Agenda Tool Dave Fisher
  • Re: Fail to submit report for iotdb and tsfile through the online Board Agenda Tool Yuan Tian
  • Re: Fail to submit report for iotdb and tsfile through the online Board Agenda Tool Yuan Tian
  • Re: Fail to submit report for iotdb and tsfile through the online Board Agenda Tool sebb
  • Re: Fail to submit report for iotdb and tsfile through the online Board Agenda Tool Yuan Tian
  • Re: Fail to submit report for iotdb and tsfile through the online Board Agenda Tool Dave Fisher
• [PR] Fix: Correct placement of metadata timestamp update in update_metadata() (tooling-trusted-releases) via GitHub
  • Re: [PR] Fix: Correct placement of metadata timestamp update in update_metadata() (tooling-trusted-releases) via GitHub
  • Re: [PR] Fix: Correct placement of metadata timestamp update in update_metadata() (tooling-trusted-releases) via GitHub
  • Re: [PR] Fix: Correct placement of metadata timestamp update in update_metadata() (tooling-trusted-releases) via GitHub
  • Re: [PR] Fix: Correct placement of metadata timestamp update in update_metadata() (tooling-trusted-releases) via GitHub
• Abhay Raj Srivastava – Interested in Trusted Releases (new contributor) Abhay Raj Srivastava
  • Re: Abhay Raj Srivastava – Interested in Trusted Releases (new contributor) Andrew Musselman
• [PR] Catch up and pass tests (tooling-trusted-releases) via GitHub
  • Re: [PR] Catch up and pass tests (tooling-trusted-releases) via GitHub
• [PR] Sync up branch (tooling-trusted-releases) via GitHub
  • Re: [PR] Sync up branch (tooling-trusted-releases) via GitHub
• [PR] Add subscription details to the README #376 (tooling-trusted-releases) via GitHub
  • Re: [PR] Add subscription details to the README #376 (tooling-trusted-releases) via GitHub
  • Re: [PR] Add subscription details to the README #376 (tooling-trusted-releases) via GitHub
• [PR] Add top nav bar (tooling-trusted-releases) via GitHub
  • Re: [PR] Add top nav bar (tooling-trusted-releases) via GitHub
  • Re: [PR] Add top nav bar (tooling-trusted-releases) via GitHub
  • Re: [PR] Add top nav bar (tooling-trusted-releases) via GitHub
  • Re: [PR] Add top nav bar (tooling-trusted-releases) via GitHub
  • Re: [PR] Add top nav bar (tooling-trusted-releases) via GitHub
  • Re: [PR] Add top nav bar (tooling-trusted-releases) via GitHub
  • Re: [PR] Add top nav bar (tooling-trusted-releases) via GitHub
  • Re: [PR] Add top nav bar (tooling-trusted-releases) via GitHub
• [I] Add subscription details to the README (tooling-trusted-releases) via GitHub
  • Re: [I] Add subscription details to the README (tooling-trusted-releases) via GitHub
• [I] Update pre-commit lint to use uv and act on push (tooling-docs) via GitHub
• [I] Decide on a type ignore format (tooling-trusted-releases) via GitHub
  • Re: [I] Decide on a type ignore format (tooling-trusted-releases) via GitHub
  • Re: [I] Decide on a type ignore format (tooling-trusted-releases) via GitHub
• [PR] Menu adjustments (tooling-docs) via GitHub
  • Re: [PR] Menu adjustments (tooling-docs) via GitHub
  • Re: [PR] Menu adjustments (tooling-docs) via GitHub
• [PR] Top navbar sticks to top (tooling-docs) via GitHub
  • Re: [PR] Top navbar sticks to top (tooling-docs) via GitHub
• [PR] Cleanup page templates (tooling-docs) via GitHub
  • Re: [PR] Cleanup page templates (tooling-docs) via GitHub
• [PR] fixed the non-functional navbar on the index page (tooling-docs) via GitHub
  • [GH] fixed the non-functional navbar on the index page (tooling-docs) via GitHub
  • Re: [PR] fixed the non-functional navbar on the index page (tooling-docs) via GitHub
  • [GH] fixed the non-functional navbar on the index page (tooling-docs) via GitHub
  • Re: [PR] fixed the non-functional navbar on the index page (tooling-docs) via GitHub
  • [GH] fixed the non-functional navbar on the index page (tooling-docs) via GitHub
  • Re: [PR] fixed the non-functional navbar on the index page (tooling-docs) via GitHub
  • Re: [PR] fixed the non-functional navbar on the index page (tooling-docs) via GitHub
• [PR] Record timestamp when committees are automatically updated (tooling-trusted-releases) via GitHub
  • Re: [PR] Record timestamp when committees are automatically updated (tooling-trusted-releases) via GitHub
  • Re: [PR] Record timestamp when committees are automatically updated (tooling-trusted-releases) via GitHub
  • Re: [PR] Record timestamp when committees are automatically updated (tooling-trusted-releases) via GitHub
  • Re: [PR] Record timestamp when committees are automatically updated (tooling-trusted-releases) 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
• [PR] Change to navbar light (tooling-docs) via GitHub
  • Re: [PR] Change to navbar light (tooling-docs) via GitHub
• [PR] Upgrade tooling to use `uv` and `pyproject.toml` (tooling-docs) via GitHub
  • Re: [PR] Upgrade tooling to use `uv` and `pyproject.toml` (tooling-docs) via GitHub
  • [GH] Upgrade tooling to use `uv` and `pyproject.toml` (tooling-docs) via GitHub
  • Re: [PR] Upgrade tooling to use `uv` and `pyproject.toml` (tooling-docs) via GitHub
• [PR] html validation fixup (tooling-docs) via GitHub
  • Re: [PR] html validation fixup (tooling-docs) via GitHub
• [I] We could add the pull request labeler an action for automatically labelling pull requests (tooling-trusted-releases) via GitHub
  • Re: [I] We could add the pull request labeler an action for automatically labelling pull requests (tooling-trusted-releases) via GitHub
  • Re: [I] We could add the pull request labeler an action for automatically labelling pull requests (tooling-trusted-releases) via GitHub
  • Re: [I] We could add the pull request labeler an action for automatically labelling pull requests (tooling-trusted-releases) via GitHub
  • Re: [I] We could add the pull request labeler an action for automatically labelling pull requests (tooling-trusted-releases) via GitHub
  • Re: [I] We could add the pull request labeler an action for automatically labelling pull requests (tooling-trusted-releases) via GitHub
  • Re: [I] We could add the pull request labeler an action for automatically labelling pull requests (tooling-trusted-releases) via GitHub
  • Re: [I] We could add the pull request labeler an action for automatically labelling pull requests (tooling-trusted-releases) via GitHub
  • Re: [I] We could add the pull request labeler an action for automatically labelling pull requests (tooling-trusted-releases) via GitHub
  • Re: [I] We could add the pull request labeler an action for automatically labelling pull requests (tooling-trusted-releases) via GitHub
  • Re: [I] We could add the pull request labeler an action for automatically labelling pull requests (tooling-trusted-releases) via GitHub
• [PR] docs: add slack link, fix list numbers, cleanup (tooling-docs) via GitHub
  • Re: [PR] docs: add slack link, fix list numbers, cleanup (tooling-docs) via GitHub
• [I] Header nav bar: Background and foreground colors do not have a sufficient contrast ratio (tooling-docs) via GitHub
  • Re: [I] Header nav bar: Background and foreground colors do not have a sufficient contrast ratio (tooling-docs) via GitHub
• [I] HTML validator: 1 error and 3 warnings for homepage (tooling-docs) via GitHub
  • Re: [I] HTML validator: 1 error and 3 warnings for homepage (tooling-docs) via GitHub
• [PR] Configure EditorConfig for `sh`, `yaml`, `yml` (tooling-docs) via GitHub
  • Re: [PR] Configure EditorConfig for `sh`, `yaml`, `yml` (tooling-docs) via GitHub
• [I] HTML markup `meta` and `title` tags: Readability and Clarity / Search Engine Optimization / Accessibility (tooling-trusted-releases) via GitHub
  • Re: [I] HTML markup `meta` and `title` tags: Readability and Clarity / Search Engine Optimization / Accessibility (tooling-trusted-releases) via GitHub
  • Re: [I] HTML markup `meta` and `title` tags: Readability and Clarity / Search Engine Optimization / Accessibility (tooling-trusted-releases) via GitHub
  • Re: [I] HTML markup `meta` and `title` tags: Readability and Clarity / Search Engine Optimization / Accessibility (tooling-trusted-releases) via GitHub
  • Re: [I] HTML markup `meta` and `title` tags: Readability and Clarity / Search Engine Optimization / Accessibility (tooling-trusted-releases) via GitHub
  • Re: [I] HTML markup `meta` and `title` tags: Readability and Clarity / Search Engine Optimization / Accessibility (tooling-trusted-releases) via GitHub
  • Re: [I] HTML markup `meta` and `title` tags: Readability and Clarity / Search Engine Optimization / Accessibility (tooling-trusted-releases) via GitHub
  • Re: [I] HTML markup `meta` and `title` tags: Readability and Clarity / Search Engine Optimization / Accessibility (tooling-trusted-releases) via GitHub
• [PR] Adding mermaid support (tooling-docs) via GitHub
  • Re: [PR] Adding mermaid support (tooling-docs) via GitHub
  • Re: [PR] Adding mermaid support (tooling-docs) via GitHub
  • Re: [PR] Adding mermaid support (tooling-docs) via GitHub
  • Re: [PR] Adding mermaid support (tooling-docs) via GitHub
  • Re: [PR] Adding mermaid support (tooling-docs) via GitHub
  • Re: [PR] Adding mermaid support (tooling-docs) via GitHub
• [PR] Cleanup markdownlint and pre-commit configuration (tooling-docs) via GitHub
  • Re: [PR] Cleanup markdownlint and pre-commit configuration (tooling-docs) via GitHub
  • [GH] Cleanup markdownlint and pre-commit configuration (tooling-docs) via GitHub
• [I] We could add a `Dependabot` config for `actions` updates (tooling-docs) via GitHub
  • Re: [I] We could add a `Dependabot` config for `actions` updates (tooling-docs) via GitHub
  • Re: [I] We could add a `Dependabot` config for `actions` updates (tooling-docs) via GitHub
  • Re: [I] We could add a `Dependabot` config for `actions` updates (tooling-docs) via GitHub
  • Re: [I] We could add a `Dependabot` config for `actions` updates (tooling-docs) via GitHub
• [PR] gha: pin `actions/checkout` to hash for v6.0.0 (tooling-docs) via GitHub
  • Re: [PR] gha: pin `actions/checkout` to hash for v6.0.0 (tooling-docs) via GitHub
• [PR] Configure Python for EditorConfig (tooling-trusted-releases) via GitHub
  • Re: [PR] Configure Python for EditorConfig (tooling-trusted-releases) via GitHub
  • Re: [PR] Configure Python for EditorConfig (tooling-trusted-releases) via GitHub
• [PR] Add alt attribute to img tag in menu (tooling-docs) via GitHub
  • Re: [PR] Add alt attribute to img tag in menu (tooling-docs) via GitHub
  • Re: [PR] Add alt attribute to img tag in menu (tooling-docs) via GitHub
• [PR] README: Remove minor underline from workflow buttons (tooling-trusted-releases) via GitHub
  • Re: [PR] README: Remove minor underline from workflow buttons (tooling-trusted-releases) via GitHub
  • Re: [PR] README: Remove minor underline from workflow buttons (tooling-trusted-releases) via GitHub
• [PR] gha: bump actions `cache`, `checkout` and `setup-python` (tooling-trusted-releases) via GitHub
  • Re: [PR] gha: bump actions `cache`, `checkout` and `setup-python` (tooling-trusted-releases) via GitHub
  • Re: [PR] gha: bump actions `cache`, `checkout` and `setup-python` (tooling-trusted-releases) via GitHub
• [PR] pre-commit: add `oxipng` for lossless PNG compression (tooling-trusted-releases) via GitHub
  • Re: [PR] pre-commit: add `oxipng` for lossless PNG compression (tooling-trusted-releases) via GitHub
  • Re: [PR] pre-commit: add `oxipng` for lossless PNG compression (tooling-trusted-releases) via GitHub
  • Re: [PR] pre-commit: add `oxipng` for lossless PNG compression (tooling-trusted-releases) via GitHub
  • Re: [PR] pre-commit: add `oxipng` for lossless PNG compression (tooling-trusted-releases) via GitHub
• [I] Provide clear instructions for running pre-check locally (tooling-docs) via GitHub
  • Re: [I] Provide clear instructions for running pre-check locally (tooling-docs) via GitHub
  • Re: [I] Provide clear instructions for running pre-check locally (tooling-docs) via GitHub
  • Re: [I] Provide clear instructions for running pre-check locally (tooling-docs) via GitHub
  • Re: [I] Provide clear instructions for running pre-check locally (tooling-docs) via GitHub
  • Re: [I] Provide clear instructions for running pre-check locally (tooling-docs) via GitHub
  • Re: [I] Provide clear instructions for running pre-check locally (tooling-docs) via GitHub
  • Re: [I] Provide clear instructions for running pre-check locally (tooling-docs) via GitHub
  • Re: [I] Provide clear instructions for running pre-check locally (tooling-docs) via GitHub
• [PR] Test markdown lint update (tooling-docs) via GitHub
  • Re: [PR] Test markdown lint update (tooling-docs) via GitHub
• [I] Add a check to ensure that the source in tarballs is the same as the upstream repository (tooling-trusted-releases) via GitHub
  • Re: [I] Add a check to ensure that the source in tarballs is the same as the upstream repository (tooling-trusted-releases) via GitHub
  • Re: [I] Add a check to ensure that the source in tarballs is the same as the upstream repository (tooling-trusted-releases) via GitHub
  • Re: [I] Add a check to ensure that the source in tarballs is the same as the upstream repository (tooling-trusted-releases) via GitHub
  • Re: [I] Add a check to ensure that the source in tarballs is the same as the upstream repository (tooling-trusted-releases) via GitHub
  • Re: [I] Add a check to ensure that the source in tarballs is the same as the upstream repository (tooling-trusted-releases) via GitHub
  • Re: [I] Add a check to ensure that the source in tarballs is the same as the upstream repository (tooling-trusted-releases) via GitHub
  • Re: [I] Add a check to ensure that the source in uploaded archives is a subset of the upstream repository (tooling-trusted-releases) via GitHub
  • Re: [I] Add a check to ensure that the source in uploaded archives is a subset of the upstream repository (tooling-trusted-releases) via GitHub
  • Re: [I] Add a check to ensure that the source in uploaded archives is a subset of the upstream repository (tooling-trusted-releases) via GitHub
  • Re: [I] Add a check to ensure that the source in uploaded archives is a subset of the upstream repository (tooling-trusted-releases) via GitHub
  • Re: [I] Add a check to ensure that the source in uploaded archives is a subset of the upstream repository (tooling-trusted-releases) via GitHub
  • Re: [I] Add a check to ensure that the source in uploaded archives is a subset of the upstream repository (tooling-trusted-releases) via GitHub
• [I] We should add `Hadolint` a Dockerfile linter, validate inline bash, written in Haskell (tooling-trusted-releases) via GitHub
  • Re: [I] We should add `Hadolint` a Dockerfile linter, validate inline bash, written in Haskell (tooling-trusted-releases) via GitHub
  • Re: [I] We should add `Hadolint` a Dockerfile linter, validate inline bash, written in Haskell (tooling-trusted-releases) via GitHub
  • Re: [I] We should add `Hadolint` a Dockerfile linter, validate inline bash, written in Haskell (tooling-trusted-releases) via GitHub
• [I] Should we add Bandit ? A tool designed to find common security issues in Python code (tooling-trusted-releases) via GitHub
  • Re: [I] Should we add Bandit ? A tool designed to find common security issues in Python code (tooling-trusted-releases) via GitHub
  • Re: [I] Should we add Bandit ? A tool designed to find common security issues in Python code (tooling-trusted-releases) via GitHub
  • Re: [I] Should we add Bandit ? A tool designed to find common security issues in Python code (tooling-trusted-releases) via GitHub
  • Re: [I] Should we add Bandit ? A tool designed to find common security issues in Python code (tooling-trusted-releases) via GitHub
  • Re: [I] Should we add Bandit ? A tool designed to find common security issues in Python code (tooling-trusted-releases) via GitHub
• Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
• Re: [I] Track creator and editor asf user ids in the database (tooling-trusted-releases) via GitHub
  • Re: [I] Track creator and editor asf user ids in the database (tooling-trusted-releases) via GitHub
• [I] Record when committees are automatically updated (tooling-trusted-releases) via GitHub
  • Re: [I] Record when committees are automatically updated (tooling-trusted-releases) via GitHub
  • Re: [I] Record when committees are automatically updated (tooling-trusted-releases) via GitHub
  • Re: [I] Record when committees are automatically updated (tooling-trusted-releases) via GitHub
• Re: [I] Add REVISION as a usable variable in emails (tooling-trusted-releases) via GitHub
  • Re: [I] Add REVISION as a usable variable in emails (tooling-trusted-releases) via GitHub
  • Re: [I] Add REVISION as a usable variable in emails (tooling-trusted-releases) via GitHub
• [I] Allow substitution variables to be used in email subjects (tooling-trusted-releases) via GitHub
  • Re: [I] Allow substitution variables to be used in email subjects (tooling-trusted-releases) via GitHub
  • Re: [I] Allow substitution variables to be used in email subjects (tooling-trusted-releases) via GitHub
  • Re: [I] Allow substitution variables to be used in email subjects (tooling-trusted-releases) via GitHub
  • Re: [I] Allow substitution variables to be used in email subjects (tooling-trusted-releases) via GitHub

• Earlier messages
• Later messages