One of the PMC member should be involved for svn side things. AFAIK, that is recommended.
Sheng Wu 吴晟 Apache SkyWalking Twitter, wusheng1108 tison <[email protected]>于2024年2月7日 周三13:48写道： > I suggest we ask the INFRA first to see if there is any blocker for > "Changing the distribution policy". > > > if an RM is a committer but not a PMC > > not a PMC member :D > > Best, > tison. > > Xuanwo <[email protected]> 于2024年2月7日周三 10:08写道： > > > > Hi, everyone > > > > I started this discussion about OpenDAL's distribution policy at > https://dist.apache.org (shortened as d.a.o) release branch. > > > > While in the incubator, all committers have direct write access to d.a.o > release branch, meaning PMCs don't need to do extra work if the RM is a > committer. > > > > However, once OpenDAL becomes a TLP, only PMCs will have write access to > d.a.o release branch. As noted in > https://github.com/apache/opendal/issues/4150, if an RM is a committer > but not a PMC, we'll need a PMC member involved in the release process to > update the KEYS and manage the release branch. > > > > We have two options here: > > > > - Change the release process: Involve a PMC member in the release > process. > > - Change the distribution policy: Allow committers to write release > branch of d.a.o (the same as before) > > > > What do you think? Feel free to leave your comments and decision below. > > > > Xuanwo >
