[DISCUSS] Open SVN dist access to committers

Hello, For the last two releases ([1] and [2]) committers were not able to finalize the release due to SVN restrictions. One of the PMC members had to step in order to distribute the artifacts. By default, only PMCs are allowed to make changes to dist

Re: [DISCUSS] Open SVN dist access to committers

+1 Clearly committers should have read and write access to all non-private information in a project. I don’t even think this needs a vote. If this discussion quickly reaches consensus, as I assume it will, let’s just make it so. The hypothetical risk that a committer would (accidentally or del

Re: [DISCUSS] Open SVN dist access to committers

On 2020/08/13 18:47:54, Julian Hyde wrote: > +1 > > Clearly committers should have read and write access to all non-private > information in a project. I don’t even think this needs a vote. If this > discussion quickly reaches consensus, as I assume it will, let’s just make it > so. > > T

Re: [DISCUSS] Open SVN dist access to committers

+1 I always thought that committers had access to the dist repo and I was completely fine with it. Everybody makes mistakes no matter if it is a committer or PMC so I don't see a reason to have different read/write access to the repo. Best, Stamatis On Fri, Aug 14, 2020 at 12:17 AM sebbaz wrot

Re: [DISCUSS] Open SVN dist access to committers

+1 if well used/tested svn commands for releasing are documented, committers without experience on release or svn can still use those properly. -Rui On Thu, Aug 13, 2020 at 3:09 PM Stamatis Zampetakis wrote: > +1 > > I always thought that committers had access to the dist repo and I was > com

Re: [DISCUSS] Open SVN dist access to committers

+1 Apart from the reasons already mentioned, if we want committers (not just PMC) to get involved in the release management process, I think this step would go in the right direction. Best regards, Ruben Le jeu. 13 août 2020 à 23:18, Rui Wang a écrit : > +1 > > if well used/tested svn command

Re: [DISCUSS] Open SVN dist access to committers

+1 from me as well. From our side, the risk is minimized as the process to move the artifacts on SVN is automated using Vladimir's gradle plugin, so there shouldn't be any manual intervention on the part of the RM. Francis On 14/08/2020 8:34 am, Ruben Q L wrote: +1 Apart from the reasons alr

Re: [DISCUSS] Open SVN dist access to committers

Thanks for the clarification, Sebb. We now know, and accept, that the risk is non-zero. > On Aug 13, 2020, at 2:17 PM, sebbaz wrote: > > > > On 2020/08/13 18:47:54, Julian Hyde wrote: >> +1 >> >> Clearly committers should have read and write access to all non-private >> information in a p

Re: [DISCUSS] Open SVN dist access to committers

Awesome! It really helps for the committers as release manager. Best, Chunwei On Fri, Aug 14, 2020 at 6:58 AM Julian Hyde wrote: > Thanks for the clarification, Sebb. We now know, and accept, that the risk > is non-zero. > > > On Aug 13, 2020, at 2:17 PM, sebbaz wrote: > > > > > > > > On 2020

Re: [DISCUSS] Open SVN dist access to committers

If you trust a committer enough to do release management, why are they not on the PMC? On 2020/08/13 22:52:55, Francis Chuang wrote: > +1 from me as well. From our side, the risk is minimized as the process > to move the artifacts on SVN is automated using Vladimir's gradle > plugin, so there