dave2wave commented on issue #523:
URL:
https://github.com/apache/tooling-trusted-releases/issues/523#issuecomment-3814140049
Today, Sean and I discussed amoung other things how to deal with the list of
PMCs where “Committers May Release” - the list is short and has had 3 additions
in the last 4 years. Druid and Hive plus Solr was split out of Lucene which is
also on the list. Commit messages led me to some JIRA issues.
- 2025 INFRA-27113: Hive committers may release
- 2023 Druid allowing committers to release
- 2023 Solr committers can release INFRA-24485
For Hive the driving message was the lack of convenience. For Druid I've yet
to find the thread, but at the time they were pushing on requirements to allow
contributors to do something.
Here's the list with the number of committers and PMC members for each:
```
bookkeeper: present (count = {'members': 32, 'owners': 20})
calcite: present (count = {'members': 81, 'owners': 32})
camel: present (count = {'members': 94, 'owners': 48})
commons: present (count = {'members': 150, 'owners': 44})
couchdb: present (count = {'members': 73, 'owners': 18})
druid: present (count = {'members': 75, 'owners': 40})
hive: present (count = {'members': 113, 'owners': 59})
lucene: present (count = {'members': 111, 'owners': 70})
solr: present (count = {'members': 99, 'owners': 62})
zookeeper: present (count = {'members': 34, 'owners': 19})
```
While I was going to communicate with each about whether this was needed or
not, instead I'm going to make it so that the "Committers May Release" list
impacts which permissions to use to "Start a Release". On the start form the
release managers are named and these may always include non PMC member
committers.
This means that many POST permissions should be changed from
`CommitteeMember` or `CommitteeParticipant` to a new `CommitteeReleaseManager`.
The new ReleaseManager class merges the CommitteeMember and any individuals
explicitly mentioned on the Release's Release Manager list which is validated
vs. CommitteeParticipant.
--
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]
