dave2wave opened a new issue, #523: URL: https://github.com/apache/tooling-trusted-releases/issues/523
The legacy term for "Release Manager" is about who has permissions to promote releases for a project. In nearly all cases this is any PMC member. A select list of PMCs have enabled their committers to promote as well. https://github.com/apache/infrastructure-svnauthz/blob/master/gen.py#L37-L50 [gen.py](https://github.com/apache/infrastructure-svnauthz/blob/master/gen.py) ``` COMMITTERS_MAY_RELEASE = { 'abdera', 'bookkeeper', 'calcite', 'camel', 'commons', 'couchdb', 'druid', 'hive', 'lucene', 'solr', 'trafficcontrol', 'zookeeper', } ``` 1. We will need an admin page to maintain this list. 2. We will need to consider storage permissions covering permission on: - release version - add individuals with #520 designations. - project - committee 4. We then need to apply this new permission appropriately to our endpoints following the skeleton in #242 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
