dist access for release

[Julien Le Dem <ju...@dremio.com>]

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 PMC + named individuals; its either PMC or Committers.)

Let me know what you decide."

I think it is fine to give access to committers in general and not just PMC
so that committers can manage the release.
It doesn't change that we need a release vote to publish anything there.

agreed?

-- 
Julien

Re: dist access for release

[Julian Hyde <jh...@apache.org>]

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 <ju...@dremio.com> wrote:
> 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
> <https://issues.apache.org/jira/browse/INFRA> referencing the PMC vote."
> So the question is, do we want to do such a vote or do we stick with "a PMC
> member will do it"?
>
> On Fri, Feb 17, 2017 at 7:39 PM, Wes McKinney <we...@gmail.com> wrote:
>
>> I'm available tomorrow to help with publishing the release artifacts.
>>
>> On Fri, Feb 17, 2017 at 9:10 PM Julian Hyde <jh...@apache.org> 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 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 to ask
>> > a PMC member to do the actual release publication.” [2]
>> >
>> > Julian
>> >
>> > [1] http://www.apache.org/legal/release-policy.html#release-distribution
>> >
>> > [2] http://www.apache.org/legal/release-policy.html#upload-ci
>> >
>> >
>> > > On Feb 17, 2017, at 5:36 PM, Julien Le Dem <ju...@dremio.com> wrote:
>> > >
>> > > 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 PMC + named individuals; its either PMC or Committers.)
>> > >
>> > > Let me know what you decide."
>> > >
>> > > I think it is fine to give access to committers in general and not just
>> > PMC
>> > > so that committers can manage the release.
>> > > It doesn't change that we need a release vote to publish anything
>> there.
>> > >
>> > > agreed?
>> > >
>> > > --
>> > > Julien
>> >
>>
>
>
>
> --
> Julien

Re: dist access for release

[Julien Le Dem <ju...@dremio.com>]

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
<https://issues.apache.org/jira/browse/INFRA> referencing the PMC vote."
So the question is, do we want to do such a vote or do we stick with "a PMC
member will do it"?

On Fri, Feb 17, 2017 at 7:39 PM, Wes McKinney <we...@gmail.com> wrote:

> I'm available tomorrow to help with publishing the release artifacts.
>
> On Fri, Feb 17, 2017 at 9:10 PM Julian Hyde <jh...@apache.org> 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 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 to ask
> > a PMC member to do the actual release publication.” [2]
> >
> > Julian
> >
> > [1] http://www.apache.org/legal/release-policy.html#release-distribution
> >
> > [2] http://www.apache.org/legal/release-policy.html#upload-ci
> >
> >
> > > On Feb 17, 2017, at 5:36 PM, Julien Le Dem <ju...@dremio.com> wrote:
> > >
> > > 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 PMC + named individuals; its either PMC or Committers.)
> > >
> > > Let me know what you decide."
> > >
> > > I think it is fine to give access to committers in general and not just
> > PMC
> > > so that committers can manage the release.
> > > It doesn't change that we need a release vote to publish anything
> there.
> > >
> > > agreed?
> > >
> > > --
> > > Julien
> >
>



-- 
Julien

Re: dist access for release

[Wes McKinney <we...@gmail.com>]

I'm available tomorrow to help with publishing the release artifacts.

On Fri, Feb 17, 2017 at 9:10 PM Julian Hyde <jh...@apache.org> 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 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 to ask
> a PMC member to do the actual release publication.” [2]
>
> Julian
>
> [1] http://www.apache.org/legal/release-policy.html#release-distribution
>
> [2] http://www.apache.org/legal/release-policy.html#upload-ci
>
>
> > On Feb 17, 2017, at 5:36 PM, Julien Le Dem <ju...@dremio.com> wrote:
> >
> > 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 PMC + named individuals; its either PMC or Committers.)
> >
> > Let me know what you decide."
> >
> > I think it is fine to give access to committers in general and not just
> PMC
> > so that committers can manage the release.
> > It doesn't change that we need a release vote to publish anything there.
> >
> > agreed?
> >
> > --
> > Julien
>

Re: dist access for release

[Julian Hyde <jh...@apache.org>]

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 to ask a PMC member to do the actual release publication.” [2]

Julian 

[1] http://www.apache.org/legal/release-policy.html#release-distribution

[2] http://www.apache.org/legal/release-policy.html#upload-ci


> On Feb 17, 2017, at 5:36 PM, Julien Le Dem <ju...@dremio.com> wrote:
> 
> 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 PMC + named individuals; its either PMC or Committers.)
> 
> Let me know what you decide."
> 
> I think it is fine to give access to committers in general and not just PMC
> so that committers can manage the release.
> It doesn't change that we need a release vote to publish anything there.
> 
> agreed?
> 
> -- 
> Julien