dev  

Messages by Thread

• • Re: [I] Implement PyPi Distributions (tooling-trusted-releases) via GitHub
  • Re: [I] Implement PyPi Distributions (tooling-trusted-releases) via GitHub
  • Re: [I] Implement PyPi Distributions (tooling-trusted-releases) via GitHub
  • Re: [I] Implement PyPi Distributions (tooling-trusted-releases) via GitHub
• Re: [I] Replace public release and committee pages with a catalog page (tooling-trusted-releases) via GitHub
• Re: [I] Tie ATR server into the rsync path of svn dist artifacts (tooling-trusted-releases) via GitHub
  • Re: [I] Tie ATR server into the rsync path of svn dist artifacts (tooling-trusted-releases) via GitHub
  • Re: [I] Tie ATR server into the rsync path of svn dist artifacts (tooling-trusted-releases) via GitHub
• Re: [I] Provide an api to artifact catalog (tooling-trusted-releases) via GitHub
  • Re: [I] Provide an api to artifact catalog (tooling-trusted-releases) via GitHub
• Re: [I] Allow Projects to be defined via .asf.yaml (tooling-trusted-releases) via GitHub
  • Re: [I] Allow Projects to be defined via .asf.yaml (tooling-trusted-releases) via GitHub
  • Re: [I] Allow Projects to be defined via .asf.yaml (tooling-trusted-releases) via GitHub
  • Re: [I] Allow Projects to be defined via .asf.yaml (tooling-trusted-releases) via GitHub
  • Re: [I] Allow Projects to be defined via .asf.yaml (tooling-trusted-releases) via GitHub
• [I] Watch svn dist releases and catalog changes to projects and releases (tooling-trusted-releases) via GitHub
  • Re: [I] Watch svn dist releases and catalog changes to projects and releases (tooling-trusted-releases) via GitHub
• Meta bug report Jens Geyer
  • Re: Meta bug report Andrew Wetmore
  • Re: Meta bug report Andrew Wetmore
  • Re: Meta bug report Thomas Neidhart
  • Re: Meta bug report Thomas Neidhart
• [I] Catalog projects and releases for each PMC from current data (tooling-trusted-releases) via GitHub
• [I] Document identification of generated source files in lightweight and RAT license checks (tooling-trusted-releases) via GitHub
  • Re: [I] Document identification of generated source files in lightweight and RAT license checks (tooling-trusted-releases) via GitHub
  • Re: [I] Document identification of generated source files in lightweight and RAT license checks (tooling-trusted-releases) via GitHub
  • Re: [I] Document identification of generated source files in lightweight and RAT license checks (tooling-trusted-releases) via GitHub
  • Re: [I] Document identification of generated source files in lightweight and RAT license checks (tooling-trusted-releases) via GitHub
  • Re: [I] Document identification of generated source files in lightweight and RAT license checks (tooling-trusted-releases) via GitHub
  • Re: [I] Document identification of generated source files in lightweight and RAT license checks (tooling-trusted-releases) via GitHub
• [I] Download rsync candidate files by a select tag (tooling-trusted-releases) via GitHub
  • Re: [I] Download rsync candidate files by a select tag (tooling-trusted-releases) via GitHub
  • Re: [I] Download rsync candidate files by a select tag (tooling-trusted-releases) via GitHub
• [I] Allow files to be tagged in the compose phase according to a mapping (tooling-trusted-releases) via GitHub
  • Re: [I] Allow files to be tagged in the compose phase according to a mapping (tooling-trusted-releases) via GitHub
  • Re: [I] Allow files to be tagged in the compose phase according to a mapping (tooling-trusted-releases) via GitHub
  • Re: [I] Allow files to be tagged in the compose phase according to a mapping (tooling-trusted-releases) via GitHub
  • Re: [I] Allow files to be tagged in the compose phase according to a mapping (tooling-trusted-releases) via GitHub
  • Re: [I] Allow files to be tagged in the compose phase according to a mapping (tooling-trusted-releases) via GitHub
  • Re: [I] Allow files to be tagged in the compose phase according to a mapping (tooling-trusted-releases) via GitHub
  • Re: [I] Allow files to be tagged in the compose phase according to a mapping (tooling-trusted-releases) via GitHub
  • Re: [I] Allow files to be tagged in the compose phase according to a mapping (tooling-trusted-releases) via GitHub
  • Re: [I] Allow files to be tagged in the compose phase according to a mapping (tooling-trusted-releases) via GitHub
• [PR] Warn user when preserve download files is enabled during announce (tooling-trusted-releases) via GitHub
  • Re: [PR] Warn user when preserve download files is enabled during announce (tooling-trusted-releases) via GitHub
  • Re: [PR] Warn user when preserve download files is enabled during announce (tooling-trusted-releases) via GitHub
  • Re: [PR] Warn user when preserve download files is enabled during announce (tooling-trusted-releases) via GitHub
  • Re: [PR] Warn user when preserve download files is enabled during announce (tooling-trusted-releases) via GitHub
  • Re: [PR] Warn user when preserve download files is enabled during announce (tooling-trusted-releases) via GitHub
  • Re: [PR] Warn user when preserve download files is enabled during announce (tooling-trusted-releases) via GitHub
  • Re: [PR] Warn user when preserve download files is enabled during announce (tooling-trusted-releases) via GitHub
• Re: [I] Implement RAO / Maven connectivity (tooling-trusted-releases) via GitHub
  • Re: [I] Implement RAO / Maven connectivity (tooling-trusted-releases) via GitHub
  • Re: [I] Implement RAO / Maven connectivity (tooling-trusted-releases) via GitHub
  • Re: [I] Implement RAO / Maven connectivity (tooling-trusted-releases) via GitHub
  • Re: [I] Implement RAO / Maven connectivity (tooling-trusted-releases) via GitHub
  • Re: [I] Implement RAO / Maven connectivity (tooling-trusted-releases) via GitHub
• [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] Add distribution directory template to finish release policy (tooling-trusted-releases) via GitHub
  • Re: [I] Add distribution directory template to finish release policy (tooling-trusted-releases) via GitHub
  • Re: [I] Add distribution directory template to finish release policy (tooling-trusted-releases) via GitHub
  • Re: [I] Add distribution directory template to finish release policy (tooling-trusted-releases) via GitHub
  • Re: [I] Add distribution directory template to finish release policy (tooling-trusted-releases) via GitHub
• [I] Consider improving logging (tooling-trusted-releases) via GitHub
  • Re: [I] Consider improving logging (tooling-trusted-releases) via GitHub
  • Re: [I] Consider improving logging (tooling-trusted-releases) via GitHub
  • Re: [I] Consider improving logging (tooling-trusted-releases) via GitHub
  • Re: [I] Consider improving logging (tooling-trusted-releases) via GitHub
  • Re: [I] Consider improving logging (tooling-trusted-releases) via GitHub
• [I] Assure that Committee and Project metadata are validated (tooling-trusted-releases) via GitHub
• [I] Project model track (tooling-trusted-releases) via GitHub
  • Re: [I] Project model track (tooling-trusted-releases) via GitHub
  • Re: [I] Project model track (tooling-trusted-releases) via GitHub
• [I] Committee/project auto update should only include data from Whimsy (tooling-trusted-releases) via GitHub
• [I] Improve RAT checks (tooling-trusted-releases) via GitHub
  • Re: [I] Improve RAT checks (tooling-trusted-releases) via GitHub
  • Re: [I] Improve RAT checks (tooling-trusted-releases) via GitHub
  • Re: [I] Improve RAT checks (tooling-trusted-releases) via GitHub
  • Re: [I] Improve RAT checks (tooling-trusted-releases) via GitHub
  • Re: [I] Improve RAT checks (tooling-trusted-releases) via GitHub
  • Re: [I] Improve RAT checks (tooling-trusted-releases) via GitHub
• [I] Add SHA512 generation to attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Add SHA512 generation to attestations (tooling-trusted-releases) via GitHub
• [I] PMCs have a charter; projects don't (tooling-trusted-releases) via GitHub
  • Re: [I] PMCs have a charter; projects don't (tooling-trusted-releases) via GitHub
• [I] Category should be a list (tooling-trusted-releases) via GitHub
  • Re: [I] Category should be a list (tooling-trusted-releases) via GitHub
  • Re: [I] Category should be a list (tooling-trusted-releases) via GitHub
• [I] Programming language should be a list (tooling-trusted-releases) via GitHub
  • Re: [I] Programming language should be a list (tooling-trusted-releases) via GitHub
  • Re: [I] Programming language should be a list (tooling-trusted-releases) via GitHub
  • Re: [I] Programming language should be a list (tooling-trusted-releases) via GitHub
• [I] Projects don't have a chair (tooling-trusted-releases) via GitHub
  • Re: [I] Projects don't have a chair (tooling-trusted-releases) via GitHub
  • Re: [I] Projects don't have a chair (tooling-trusted-releases) via GitHub
  • Re: [I] Projects don't have a chair (tooling-trusted-releases) via GitHub
• [I] Openapi endpoint is blocked by csp (tooling-trusted-releases) via GitHub
  • Re: [I] Openapi endpoint is blocked by csp (tooling-trusted-releases) via GitHub
  • Re: [I] Openapi endpoint is blocked by csp (tooling-trusted-releases) via GitHub
• [I] Candidate phases track (tooling-trusted-releases) via GitHub
  • Re: [I] Candidate phases track (tooling-trusted-releases) via GitHub
  • Re: [I] Candidate phases track (tooling-trusted-releases) via GitHub
  • Re: [I] Candidate phases track (tooling-trusted-releases) via GitHub
• Re: [I] Record votes in the database (tooling-trusted-releases) via GitHub
• [I] Checks track (tooling-trusted-releases) via GitHub
  • Re: [I] Checks track (tooling-trusted-releases) via GitHub
• [I] Discuss identification of generated source files (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss identification of generated source files (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss identification of generated source files (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss identification of generated source files (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss identification of generated source files (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss identification of generated source files (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss identification of generated source files (tooling-trusted-releases) via GitHub
• [I] Valid NOTICE files are marked invalid (tooling-trusted-releases) via GitHub
  • Re: [I] Valid NOTICE files are marked invalid (tooling-trusted-releases) via GitHub
  • Re: [I] Valid NOTICE files are marked invalid (tooling-trusted-releases) via GitHub
  • Re: [I] Valid NOTICE files are marked invalid (tooling-trusted-releases) via GitHub
  • Re: [I] Valid NOTICE files are marked invalid (tooling-trusted-releases) via GitHub
  • Re: [I] Valid NOTICE files are marked invalid (tooling-trusted-releases) via GitHub
  • Re: [I] Valid NOTICE files are marked invalid (tooling-trusted-releases) via GitHub
  • Re: [I] Valid NOTICE files are marked invalid (tooling-trusted-releases) via GitHub
  • Re: [I] Valid NOTICE files are marked invalid (tooling-trusted-releases) via GitHub
• Re: [I] Warn the user if the "Preserve download files" option is checked during announcing (tooling-trusted-releases) via GitHub
  • Re: [I] Warn the user if the "Preserve download files" option is checked during announcing (tooling-trusted-releases) via GitHub
  • Re: [I] Warn the user if the "Preserve download files" option is checked during announcing (tooling-trusted-releases) via GitHub
  • Re: [I] Warn the user if the "Preserve download files" option is checked during announcing (tooling-trusted-releases) via GitHub
  • Re: [I] Warn the user if the "Preserve download files" option is checked during announcing (tooling-trusted-releases) via GitHub
• [PR] Record automatic committee updates in audit log (tooling-trusted-releases) via GitHub
  • Re: [PR] Record automatic committee updates in audit log (tooling-trusted-releases) via GitHub
  • Re: [PR] Record automatic committee updates in audit log (tooling-trusted-releases) via GitHub
  • Re: [PR] Record automatic committee updates in audit log (tooling-trusted-releases) via GitHub
  • Re: [PR] Record automatic committee updates in audit log (tooling-trusted-releases) via GitHub
  • [GH] Record automatic committee updates in audit log (tooling-trusted-releases) via GitHub
  • Re: [PR] Record automatic committee updates in audit log (tooling-trusted-releases) via GitHub
  • Re: [PR] Record automatic committee updates in audit log (tooling-trusted-releases) via GitHub
  • Re: [PR] Record automatic committee updates in audit log (tooling-trusted-releases) via GitHub
  • Re: [PR] Record automatic committee updates in audit log (tooling-trusted-releases) via GitHub
  • Re: [PR] Record automatic committee updates in audit log (tooling-trusted-releases) via GitHub
  • Re: [PR] Record automatic committee updates in audit log (tooling-trusted-releases) via GitHub
  • Re: [PR] Record automatic committee updates in audit log (tooling-trusted-releases) via GitHub
  • Re: [PR] Record automatic committee updates in audit log (tooling-trusted-releases) via GitHub
  • Re: [PR] Record automatic committee updates in audit log (tooling-trusted-releases) via GitHub
  • Re: [PR] Record automatic committee updates in audit log (tooling-trusted-releases) via GitHub
• [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
  • Re: [I] Project metadata to add to project database (tooling-trusted-releases) via GitHub
• [I] Binary artifacts seem to be checked for "lightweight" licence check even if RAT only is used (tooling-trusted-releases) via GitHub
  • Re: [I] Binary artifacts seem to be checked for "lightweight" licence check even if RAT only is used (tooling-trusted-releases) via GitHub
  • Re: [I] Binary artifacts seem to be checked for "lightweight" licence check even if RAT only is used (tooling-trusted-releases) via GitHub
  • Re: [I] Binary artifacts seem to be checked for "lightweight" licence check even if RAT only is used (tooling-trusted-releases) via GitHub
  • Re: [I] Binary artifacts seem to be checked for "lightweight" licence check even if RAT only is used (tooling-trusted-releases) via GitHub
  • Re: [I] Binary artifacts seem to be checked for "lightweight" licence check even if RAT only is used (tooling-trusted-releases) via GitHub
  • Re: [I] Binary artifacts seem to be checked for "lightweight" licence check even if RAT only is used (tooling-trusted-releases) via GitHub
  • Re: [I] Binary artifacts seem to be checked for "lightweight" licence check even if RAT only is used (tooling-trusted-releases) via GitHub
  • Re: [I] Binary artifacts seem to be checked for "lightweight" licence check even if RAT only is used (tooling-trusted-releases) via GitHub
  • Re: [I] Binary artifacts seem to be checked for "lightweight" licence check even if RAT only is used (tooling-trusted-releases) via GitHub
  • Re: [I] Binary artifacts seem to be checked for "lightweight" licence check even if RAT only is used (tooling-trusted-releases) via GitHub
• [I] SVN upload seems to not work (tooling-trusted-releases) via GitHub
  • Re: [I] SVN upload seems to not work (tooling-trusted-releases) via GitHub
  • Re: [I] SVN upload seems to not work (tooling-trusted-releases) via GitHub
  • Re: [I] SVN upload seems to not work (tooling-trusted-releases) via GitHub
  • Re: [I] SVN upload seems to not work (tooling-trusted-releases) via GitHub
  • Re: [I] SVN upload seems to not work (tooling-trusted-releases) via GitHub
  • Re: [I] SVN upload seems to not work (tooling-trusted-releases) via GitHub
  • Re: [I] SVN upload seems to not work (tooling-trusted-releases) via GitHub
• [I] Use Mailpit to improve email tests (tooling-trusted-releases) via GitHub
  • Re: [I] Use Mailpit to improve email tests (tooling-trusted-releases) via GitHub
  • Re: [I] Use Mailpit to improve email tests (tooling-trusted-releases) via GitHub
  • Re: [I] Use Mailpit to improve email tests (tooling-trusted-releases) via GitHub
• Re: [I] Rat check / Licence Headers check (tooling-trusted-releases) via GitHub
  • Re: [I] Rat check / Licence Headers check (tooling-trusted-releases) via GitHub
  • Re: [I] Rat check / Licence Headers check (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

• Earlier messages
• Later messages