dev  

Messages by Thread

• • Re: [I] Implement rate limiting on authentication endpoints (tooling-trusted-releases) via GitHub
  • Re: [I] Implement rate limiting on authentication endpoints (tooling-trusted-releases) via GitHub
  • Re: [I] Implement rate limiting on authentication endpoints (tooling-trusted-releases) via GitHub
  • Re: [I] Implement rate limiting on authentication endpoints (tooling-trusted-releases) via GitHub
  • Re: [I] Implement rate limiting on authentication endpoints (tooling-trusted-releases) via GitHub
  • Re: [I] Implement rate limiting on authentication endpoints (tooling-trusted-releases) via GitHub
  • Re: [I] Implement rate limiting on authentication endpoints (tooling-trusted-releases) via GitHub
  • Re: [I] Implement rate limiting on authentication endpoints (tooling-trusted-releases) via GitHub
  • Re: [I] Implement rate limiting on authentication endpoints (tooling-trusted-releases) via GitHub
  • Re: [I] Implement rate limiting on authentication endpoints (tooling-trusted-releases) via GitHub
  • Re: [I] Implement rate limiting on authentication endpoints (tooling-trusted-releases) via GitHub
  • Re: [I] Implement rate limiting on authentication endpoints (tooling-trusted-releases) via GitHub
  • Re: [I] Implement rate limiting on authentication endpoints (tooling-trusted-releases) via GitHub
  • Re: [I] Implement rate limiting on authentication endpoints (tooling-trusted-releases) via GitHub
  • Re: [I] Implement rate limiting on authentication endpoints (tooling-trusted-releases) via GitHub
  • Re: [I] Implement rate limiting on authentication endpoints (tooling-trusted-releases) via GitHub
  • Re: [I] Implement rate limiting on authentication endpoints (tooling-trusted-releases) via GitHub
  • Re: [I] Implement rate limiting on authentication endpoints (tooling-trusted-releases) via GitHub
  • Re: [I] Implement rate limiting on authentication endpoints (tooling-trusted-releases) via GitHub
• [PR] Bump pyasn1 from 0.6.1 to 0.6.2 (tooling-trusted-releases) via GitHub
  • Re: [PR] Bump pyasn1 from 0.6.1 to 0.6.2 (tooling-trusted-releases) via GitHub
  • Re: [PR] Bump pyasn1 from 0.6.1 to 0.6.2 (tooling-trusted-releases) via GitHub
• [I] Update `notes` (tooling-trusted-releases) via GitHub
  • Re: [I] Update `notes` (tooling-trusted-releases) via GitHub
  • Re: [I] Update `notes` (tooling-trusted-releases) via GitHub
  • Re: [I] Update `notes` (tooling-trusted-releases) via GitHub
• [PR] Bump pynacl from 1.6.0 to 1.6.2 (tooling-trusted-releases) via GitHub
  • Re: [PR] Bump pynacl from 1.6.0 to 1.6.2 (tooling-trusted-releases) via GitHub
  • Re: [PR] Bump pynacl from 1.6.0 to 1.6.2 (tooling-trusted-releases) via GitHub
• [PR] Migrate state files with extensive checks (tooling-trusted-releases) via GitHub
  • [GH] Migrate state files with extensive checks (tooling-trusted-releases) via GitHub
  • [GH] Migrate state files with extensive checks (tooling-trusted-releases) via GitHub
  • Re: [PR] Migrate state files with extensive checks (tooling-trusted-releases) via GitHub
  • Re: [PR] Migrate state files with extensive checks (tooling-trusted-releases) via GitHub
  • Re: [PR] Migrate state files with extensive checks (tooling-trusted-releases) via GitHub
• Re: [I] Evaluate ASVS v5.0.0 compliance: server side execution (tooling-trusted-releases) via GitHub
  • Re: [I] Evaluate ASVS v5.0.0 compliance: server side execution (tooling-trusted-releases) via GitHub
  • Re: [I] Evaluate ASVS v5.0.0 compliance: server side execution (tooling-trusted-releases) via GitHub
• Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
• [I] Organise all files into subdirectories within the state directory (tooling-trusted-releases) via GitHub
  • Re: [I] Organise all files into subdirectories within the state directory (tooling-trusted-releases) via GitHub
  • Re: [I] Organise all files into subdirectories within the state directory (tooling-trusted-releases) via GitHub
  • Re: [I] Organise all files into subdirectories within the state directory (tooling-trusted-releases) via GitHub
  • Re: [I] Organise all files into subdirectories within the state directory (tooling-trusted-releases) via GitHub
• [PR] Possible recurrent jobs implementation (tooling-trusted-releases) via GitHub
  • Re: [PR] Possible recurrent jobs implementation (tooling-trusted-releases) via GitHub
  • [GH] Possible recurrent jobs implementation (tooling-trusted-releases) via GitHub
  • [GH] Possible recurrent jobs implementation (tooling-trusted-releases) via GitHub
  • [GH] Possible recurrent jobs implementation (tooling-trusted-releases) via GitHub
  • [GH] Possible recurrent jobs implementation (tooling-trusted-releases) via GitHub
  • [GH] Possible recurrent jobs implementation (tooling-trusted-releases) via GitHub
  • [GH] Possible recurrent jobs implementation (tooling-trusted-releases) via GitHub
  • [GH] Possible recurrent jobs implementation (tooling-trusted-releases) via GitHub
  • Re: [PR] Possible recurrent jobs implementation (tooling-trusted-releases) via GitHub
• Re: [I] Clarify and constrain permitted ASF TLP version numbers (tooling-trusted-releases) via GitHub
  • Re: [I] Clarify and constrain permitted ASF TLP version numbers (tooling-trusted-releases) via GitHub
  • Re: [I] Clarify and constrain permitted ASF TLP version numbers (tooling-trusted-releases) via GitHub
  • Re: [I] Clarify and constrain permitted ASF TLP version numbers (tooling-trusted-releases) via GitHub
• Re: [I] Ordering of private vs public functions (tooling-trusted-releases) via GitHub
  • Re: [I] Ordering of private vs public functions (tooling-trusted-releases) via GitHub
• Re: [I] Improve HTML form validation error display and code quality (tooling-trusted-releases) via GitHub
  • Re: [I] Improve HTML form validation error display and code quality (tooling-trusted-releases) via GitHub
  • Re: [I] Improve HTML form validation error display and code quality (tooling-trusted-releases) via GitHub
• [I] FAQs on ATR for legal release policy (tooling-trusted-releases) via GitHub
• [I] Incubator documentation for release management (tooling-trusted-releases) via GitHub
• Re: [I] Release policy improvements for ATR (tooling-trusted-releases) via GitHub
  • Re: [I] Release policy improvements for ATR (tooling-trusted-releases) via GitHub
  • Re: [I] Release policy improvements for ATR (tooling-trusted-releases) via GitHub
  • Re: [I] Release policy improvements for ATR (tooling-trusted-releases) via GitHub
  • Re: [I] Release policy improvements for ATR (tooling-trusted-releases) via GitHub
• [I] Infra documentation additions to describe using ATR in release creation (tooling-trusted-releases) via GitHub
• [I] Infra documentation changes for Download pages (tooling-trusted-releases) via GitHub
• [I] Infra documentation changes for the Release Manager role (tooling-trusted-releases) via GitHub
  • Re: [I] Infra documentation changes for the Release Manager role (tooling-trusted-releases) via GitHub
  • Re: [I] Infra documentation changes for the Release Manager role (tooling-trusted-releases) via GitHub
  • Re: [I] Infra documentation changes for the Release Manager role (tooling-trusted-releases) Andrew Wetmore
  • Re: [I] Infra documentation changes for the Release Manager role (tooling-trusted-releases) Andrew Wetmore
  • Re: [I] Infra documentation changes for the Release Manager role (tooling-trusted-releases) via GitHub
• Re: [I] Finish option to automatically archive prior release (tooling-trusted-releases) via GitHub
  • Re: [I] Finish option to automatically archive prior release (tooling-trusted-releases) via GitHub
  • Re: [I] Finish option to automatically archive prior release (tooling-trusted-releases) via GitHub
• [I] Promotion permissions for phase transitions and distributions (tooling-trusted-releases) via GitHub
  • Re: [I] Promotion permissions for phase transitions and distributions (tooling-trusted-releases) via GitHub
  • Re: [I] Promotion permissions for phase transitions and distributions (tooling-trusted-releases) via GitHub
  • Re: [I] Promotion permissions for phase transitions and distributions (tooling-trusted-releases) via GitHub
  • Re: [I] Promotion permissions for phase transitions and distributions (tooling-trusted-releases) via GitHub
  • Re: [I] Promotion permissions for phase transitions and distributions (tooling-trusted-releases) via GitHub
  • Re: [I] Promotion permissions for phase transitions and distributions (tooling-trusted-releases) via GitHub
  • Re: [I] Committees where committers may release (tooling-trusted-releases) via GitHub
  • Re: [I] Committees where committers may release (tooling-trusted-releases) via GitHub
• [I] Add a PR form to orient new developers (tooling-trusted-releases) via GitHub
  • Re: [I] Add a PR form to orient new developers (tooling-trusted-releases) via GitHub
  • Re: [I] Add a PR form to orient new developers (tooling-trusted-releases) via GitHub
  • Re: [I] Add a PR form to orient new developers (tooling-trusted-releases) via GitHub
  • Re: [I] Add a PR form to orient new developers (tooling-trusted-releases) via GitHub
• [I] Document the layout of the filesystem (tooling-trusted-releases) via GitHub
  • Re: [I] Document the layout of the filesystem (tooling-trusted-releases) via GitHub
  • Re: [I] Document the layout of the filesystem (tooling-trusted-releases) via GitHub
  • Re: [I] Document the layout of the filesystem (tooling-trusted-releases) via GitHub
• [I] Allow release managers to be designated (tooling-trusted-releases) via GitHub
  • Re: [I] Allow release managers to be designated (tooling-trusted-releases) via GitHub
  • Re: [I] Allow release managers to be designated (tooling-trusted-releases) via GitHub
  • Re: [I] Allow release managers to be designated (tooling-trusted-releases) via GitHub
  • Re: [I] Allow release managers to be designated (tooling-trusted-releases) via GitHub
  • Re: [I] Allow release managers to be designated (tooling-trusted-releases) via GitHub
  • Re: [I] Allow release managers to be designated (tooling-trusted-releases) via GitHub
  • Re: [I] Allow release managers to be designated (tooling-trusted-releases) via GitHub
  • Re: [I] Allow release managers to be designated (tooling-trusted-releases) via GitHub
  • Re: [I] Allow release managers to be designated (tooling-trusted-releases) via GitHub
  • Re: [I] Allow release managers to be designated (tooling-trusted-releases) via GitHub
• [PR] Document database cascade deletions (#517) (tooling-trusted-releases) via GitHub
  • Re: [PR] Document database cascade deletions (tooling-trusted-releases) via GitHub
  • Re: [PR] Document database cascade deletions (tooling-trusted-releases) via GitHub
  • Re: [PR] Document database cascade deletions (tooling-trusted-releases) via GitHub
• Re: [I] Review permissions for all actions in ATR (tooling-trusted-releases) via GitHub
  • Re: [I] Review permissions for all actions in ATR (tooling-trusted-releases) via GitHub
  • Re: [I] Review permissions for all actions in ATR (tooling-trusted-releases) via GitHub
  • Re: [I] Review permissions for all actions in ATR (tooling-trusted-releases) via GitHub
• [I] Ensure that ATR can be developed on musl based Linux distributions (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that ATR can be developed on musl based Linux distributions (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that ATR can be developed on musl based Linux distributions (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that ATR can be developed on musl based Linux distributions (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that ATR can be developed on musl based Linux distributions (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that ATR can be developed on musl based Linux distributions (tooling-trusted-releases) via GitHub
• [I] Updated Readme (tooling-actions) via GitHub
  • Re: [I] Updated Readme (tooling-actions) via GitHub
  • Re: [I] Updated Readme (tooling-actions) via GitHub
  • Re: [I] Updated Readme (tooling-actions) via GitHub
  • Re: [I] Updated Readme (tooling-actions) via GitHub
  • Re: [I] Updated Readme (tooling-actions) via GitHub
• [I] Document database cascades (tooling-trusted-releases) via GitHub
  • Re: [I] Document database cascades (tooling-trusted-releases) via GitHub
  • Re: [I] Document database cascades (tooling-trusted-releases) via GitHub
  • Re: [I] Document database cascades (tooling-trusted-releases) via GitHub
  • Re: [I] Document database cascades (tooling-trusted-releases) via GitHub
  • Re: [I] Document database cascades (tooling-trusted-releases) via GitHub
• [I] Do not allow revision serial numbers to be reallocated (tooling-trusted-releases) via GitHub
  • Re: [I] Do not allow revision serial numbers to be reallocated (tooling-trusted-releases) via GitHub
  • Re: [I] Do not allow revision serial numbers to be reallocated (tooling-trusted-releases) via GitHub
  • Re: [I] Do not allow revision serial numbers to be reallocated (tooling-trusted-releases) via GitHub
• [I] Make it less likely that release artifacts can be accidentally modified or deleted (tooling-trusted-releases) via GitHub
  • Re: [I] Make it less likely that release artifacts can be accidentally modified or deleted (tooling-trusted-releases) via GitHub
  • Re: [I] Make it less likely that release artifacts can be accidentally modified or deleted (tooling-trusted-releases) via GitHub
  • Re: [I] Make it less likely that release artifacts can be accidentally modified or deleted (tooling-trusted-releases) via GitHub
• Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
• [PR] # This is a combination of 2 commits. (tooling-trusted-releases) via GitHub
  • Re: [PR] # This is a combination of 2 commits. (tooling-trusted-releases) via GitHub
• [I] DB JDO project label is db-_jdo with an extra symbol between db and jdo (tooling-trusted-releases) via GitHub
  • Re: [I] DB JDO project label is db-_jdo with an extra symbol between db and jdo (tooling-trusted-releases) via GitHub
  • Re: [I] DB JDO project label is db-_jdo with an extra symbol between db and jdo (tooling-trusted-releases) via GitHub
  • Re: [I] DB JDO project label is db-_jdo with an extra symbol between db and jdo (tooling-trusted-releases) via GitHub
  • Re: [I] DB JDO project label is db-_jdo with an extra symbol between db and jdo (tooling-trusted-releases) via GitHub
  • Re: [I] DB JDO project label is db-_jdo with an extra symbol between db and jdo (tooling-trusted-releases) via GitHub
  • Re: [I] DB JDO project label is db-_jdo with an extra symbol between db and jdo (tooling-trusted-releases) via GitHub
  • Re: [I] DB JDO project label is db-_jdo with an extra symbol between db and jdo (tooling-trusted-releases) via GitHub
  • Re: [I] DB JDO project label is db-_jdo with an extra symbol between db and jdo (tooling-trusted-releases) via GitHub
  • Re: [I] DB JDO project label is db-_jdo with an extra symbol between db and jdo (tooling-trusted-releases) via GitHub
• Re: [I] Allow a past release to be archived when creating a new release (tooling-trusted-releases) via GitHub
• Re: [I] Improve RAT checks (tooling-trusted-releases) via GitHub
• [I] Beta track (tooling-trusted-releases) via GitHub
• Re: [I] Work on the following issues in order (tooling-trusted-releases) via GitHub
  • Re: [I] Work on the following issues in order (tooling-trusted-releases) via GitHub
• [I] Miscellaneous track (tooling-trusted-releases) via GitHub
• Re: [I] Ignore checks are ignored (tooling-trusted-releases) via GitHub
  • Re: [I] Ignore checks are ignored (tooling-trusted-releases) via GitHub
  • Re: [I] Ignore checks are ignored (tooling-trusted-releases) via GitHub
  • Re: [I] Ignore checks are ignored (tooling-trusted-releases) via GitHub
• Re: [I] /api/project/releases/{name} should return 404 for non-existent project (tooling-trusted-releases) via GitHub
  • Re: [I] /api/project/releases/{name} should return 404 for non-existent project (tooling-trusted-releases) via GitHub
  • Re: [I] /api/project/releases/{name} should return 404 for non-existent project (tooling-trusted-releases) via GitHub
• [I] Ensure that a project can only be deleted or archived under certain conditions, and that the state is clear (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that a project can only be deleted or archived under certain conditions, and that the state is clear (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that a project can only be deleted or archived under certain conditions, and that the state is clear (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that a project can only be deleted or archived under certain conditions, 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

• Later messages