You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by sebb <se...@gmail.com> on 2015/06/23 17:59:50 UTC
[DISCUSS] Karma necessary for Release Manager roles
The default karma needed for committing to the SVN dist/release/TLP
areas is membership of the LDAP PMC group. This can be changed to be
membership of the LDAP committer group if required.
I'm not sure about the current karma needed for Nexus upload, it may
be either PMC or committer membership. AFAIK this can be changed if
necessary.
I think it would be useful to allow non-PMC members to act as release manager.
This means relaxing some of the existing technical restrictions.
However I think it would too permissive to allow any ASF committer to act as RM.
Releases cannot be reverted in the same way as commits, and need a
greater degree of experience than code/doc fixes.
So I suggest that Commons agrees that membership of the LDAP Commons
committer group be regarded as sufficient karma for performing RM
tasks.
[We no longer use the LDAP Commons committer group for controlling
access to the code itself.
I think the LDAP committer group is largely redundant. This would give
it a new role.]
The PMC does not need to involve the board in changes to the committer group.
Updates to the LDAP group can be made by a PMC chair.
Apart from the actual Commons chair there are other chairs on the PMC
as well as Infra folks, so that should not be an issue once it has
been decided on the RM.
So it would be a relatively simple process to grant karma to a new RM
once any necessary technical changes have been made.
Thoughts?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [DISCUSS] Karma necessary for Release Manager roles
Posted by Phil Steitz <ph...@gmail.com>.
On 6/23/15 12:55 PM, Gary Gregory wrote:
> On Tue, Jun 23, 2015 at 12:30 PM, Stefan Bodewig <bo...@apache.org> wrote:
>
>> On 2015-06-23, Gary Gregory wrote:
>>
>>>> sebb wrote:
>>>>> I think it would be useful to allow non-PMC members to act as
>>>>> release manager. This means relaxing some of the existing technical
>>>>> restrictions.
>>> Just be clear, that would mean that any Apache Committer could release
>> any
>>> Apache Commons component.
>> ... could prepare a release and call for a vote. It would still by the
>> PMC vote that made it a release.
>>
>> This is not what Sebb suggested, aynway. He talked about re-purposing
>> the now unused Commons LDAP group for non-PMCers that are allowed to cut
>> releases.
>>
>>> On Tue, Jun 23, 2015 at 11:49 AM, Thomas Neidhart <
>> thomas.neidhart@gmail.com wrote:
>>
>>>> I think that every committer shall be able to do a release for a
>>>> commons component after it has been discussed on the mailinglist.
>> I agree, we'd still have PMC oversight.
>
> Well, no, because once you are in Nexus, you can release, so if any Apache
> Committer can push the release button, that's not PMC oversight.
You need to distinguish between access control and oversight. Until
Nexus came along, there really never was anything preventing any
commons committer from publishing release artifacts. To my
knowledge, we had just one "unsanctioned" release pushed to maven
repos (by mistake back in the wild m1 days where it was relatively
easy to inadvertently push artifacts) and we never have had a
committer not follow the process of cutting RCs and pushing only
successfully voted artifacts to the mirrors / maven repos. I don't
personally see the need to use access control to prevent committers
from circumventing the release process.
I am +0 for just letting any ASF committer RM commons releases. I
agree with Thomas, though, that help from others for new RMs is good.
The +0 vs +1 for me has to do with supporting the release. Now that
we don't vote and offer committership to ASF committers (automatic
commit), there is no acceptance of any kind provided by ASF
committers who contribute here. That's fine for CTR patches, etc;
but I would like to see a little more when it comes to a release.
Joining the PMC is probably a bigger commitment than necessary; but
it works4me to signal a connection to the project.
Phil
>
> Gary
>
>
>> The middleground suggested by
>> sebb would work for me as well, but I don't see why it would be
>> necessary.
>>
>> Stefan
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [DISCUSS] Karma necessary for Release Manager roles
Posted by Gary Gregory <ga...@gmail.com>.
On Tue, Jun 23, 2015 at 12:30 PM, Stefan Bodewig <bo...@apache.org> wrote:
> On 2015-06-23, Gary Gregory wrote:
>
> >> sebb wrote:
>
> >>> I think it would be useful to allow non-PMC members to act as
> >>> release manager. This means relaxing some of the existing technical
> >>> restrictions.
>
> > Just be clear, that would mean that any Apache Committer could release
> any
> > Apache Commons component.
>
> ... could prepare a release and call for a vote. It would still by the
> PMC vote that made it a release.
>
> This is not what Sebb suggested, aynway. He talked about re-purposing
> the now unused Commons LDAP group for non-PMCers that are allowed to cut
> releases.
>
> > On Tue, Jun 23, 2015 at 11:49 AM, Thomas Neidhart <
> thomas.neidhart@gmail.com wrote:
>
> >> I think that every committer shall be able to do a release for a
> >> commons component after it has been discussed on the mailinglist.
>
> I agree, we'd still have PMC oversight.
Well, no, because once you are in Nexus, you can release, so if any Apache
Committer can push the release button, that's not PMC oversight.
Gary
> The middleground suggested by
> sebb would work for me as well, but I don't see why it would be
> necessary.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [DISCUSS] Karma necessary for Release Manager roles
Posted by Stefan Bodewig <bo...@apache.org>.
On 2015-06-23, Gary Gregory wrote:
>> sebb wrote:
>>> I think it would be useful to allow non-PMC members to act as
>>> release manager. This means relaxing some of the existing technical
>>> restrictions.
> Just be clear, that would mean that any Apache Committer could release any
> Apache Commons component.
... could prepare a release and call for a vote. It would still by the
PMC vote that made it a release.
This is not what Sebb suggested, aynway. He talked about re-purposing
the now unused Commons LDAP group for non-PMCers that are allowed to cut
releases.
> On Tue, Jun 23, 2015 at 11:49 AM, Thomas Neidhart <thomas.neidhart@gmail.com wrote:
>> I think that every committer shall be able to do a release for a
>> commons component after it has been discussed on the mailinglist.
I agree, we'd still have PMC oversight. The middleground suggested by
sebb would work for me as well, but I don't see why it would be
necessary.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [DISCUSS] Karma necessary for Release Manager roles
Posted by Gary Gregory <ga...@gmail.com>.
On Tue, Jun 23, 2015 at 11:49 AM, Thomas Neidhart <thomas.neidhart@gmail.com
> wrote:
> On 06/23/2015 05:59 PM, sebb wrote:
> > The default karma needed for committing to the SVN dist/release/TLP
> > areas is membership of the LDAP PMC group. This can be changed to be
> > membership of the LDAP committer group if required.
> >
> > I'm not sure about the current karma needed for Nexus upload, it may
> > be either PMC or committer membership. AFAIK this can be changed if
> > necessary.
> >
> > I think it would be useful to allow non-PMC members to act as release
> manager.
> > This means relaxing some of the existing technical restrictions.
>
Just be clear, that would mean that any Apache Committer could release any
Apache Commons component.
Gary
> >
> > However I think it would too permissive to allow any ASF committer to
> act as RM.
> > Releases cannot be reverted in the same way as commits, and need a
> > greater degree of experience than code/doc fixes.
> >
> > So I suggest that Commons agrees that membership of the LDAP Commons
> > committer group be regarded as sufficient karma for performing RM
> > tasks.
> >
> > [We no longer use the LDAP Commons committer group for controlling
> > access to the code itself.
> > I think the LDAP committer group is largely redundant. This would give
> > it a new role.]
> >
> > The PMC does not need to involve the board in changes to the committer
> group.
> > Updates to the LDAP group can be made by a PMC chair.
> > Apart from the actual Commons chair there are other chairs on the PMC
> > as well as Infra folks, so that should not be an issue once it has
> > been decided on the RM.
> >
> > So it would be a relatively simple process to grant karma to a new RM
> > once any necessary technical changes have been made.
> >
> > Thoughts?
>
> I think that every committer shall be able to do a release for a commons
> component after it has been discussed on the mailinglist.
>
> Otoh, I think it would be very beneficial if at least one PMC member
> provides mentoring for somebody doing his / her first release here, as
> the process can be quite complex and frustrating.
>
> I did survive my first release only because I followed the wonderful
> release guide for math, but only few people know about it.
>
> Thomas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [DISCUSS] Karma necessary for Release Manager roles
Posted by Thomas Neidhart <th...@gmail.com>.
On 06/23/2015 05:59 PM, sebb wrote:
> The default karma needed for committing to the SVN dist/release/TLP
> areas is membership of the LDAP PMC group. This can be changed to be
> membership of the LDAP committer group if required.
>
> I'm not sure about the current karma needed for Nexus upload, it may
> be either PMC or committer membership. AFAIK this can be changed if
> necessary.
>
> I think it would be useful to allow non-PMC members to act as release manager.
> This means relaxing some of the existing technical restrictions.
>
> However I think it would too permissive to allow any ASF committer to act as RM.
> Releases cannot be reverted in the same way as commits, and need a
> greater degree of experience than code/doc fixes.
>
> So I suggest that Commons agrees that membership of the LDAP Commons
> committer group be regarded as sufficient karma for performing RM
> tasks.
>
> [We no longer use the LDAP Commons committer group for controlling
> access to the code itself.
> I think the LDAP committer group is largely redundant. This would give
> it a new role.]
>
> The PMC does not need to involve the board in changes to the committer group.
> Updates to the LDAP group can be made by a PMC chair.
> Apart from the actual Commons chair there are other chairs on the PMC
> as well as Infra folks, so that should not be an issue once it has
> been decided on the RM.
>
> So it would be a relatively simple process to grant karma to a new RM
> once any necessary technical changes have been made.
>
> Thoughts?
I think that every committer shall be able to do a release for a commons
component after it has been discussed on the mailinglist.
Otoh, I think it would be very beneficial if at least one PMC member
provides mentoring for somebody doing his / her first release here, as
the process can be quite complex and frustrating.
I did survive my first release only because I followed the wonderful
release guide for math, but only few people know about it.
Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org