Re: dist access for release

2017-02-21 Thread Julian Hyde
I have some remarks I would like to make to the PMC. I will start a new discussion on the private list. On Tue, Feb 21, 2017 at 11:10 AM, Julien Le Dem wrote: > Julian, > Thank you for pointing at the reference. I see in [2] that: > "The PMC can also vote to let

Re: dist access for release

2017-02-21 Thread Julien Le Dem
Julian, Thank you for pointing at the reference. I see in [2] that: "The PMC can also vote to let non-PMC-members update the dist/release area. To get this set up, please open a JIRA ticket at the INFRA JIRA referencing the PMC vote." So the question

Re: dist access for release

2017-02-17 Thread Wes McKinney
I'm available tomorrow to help with publishing the release artifacts. On Fri, Feb 17, 2017 at 9:10 PM Julian Hyde wrote: > No. My understanding is that only PMC members are authorized by ASF to > make a release. Committers can be release managers. > > "All release artifacts

Re: dist access for release

2017-02-17 Thread Julian Hyde
No. My understanding is that only PMC members are authorized by ASF to make a release. Committers can be release managers. "All release artifacts within the directory MUST be signed by a committer, preferably a PMC member.” [1] "If the Release Manager is not a member of the PMC, they will need

dist access for release

2017-02-17 Thread Julien Le Dem
Here is the answer from infra regarding release repo access: https://issues.apache.org/jira/browse/INFRA-13530 "So the 'default' is that PMC members have access to the dist dev/release area of a project. The PMC can request that that setting be lifted to include project committers. (We wont grant