activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robbie Gemmell <>
Subject Re: PR Process on repo
Date Wed, 12 Nov 2014 16:44:39 GMT
On 12 November 2014 16:21, Clebert Suconic <>

> I would like us to use the pull request approach on
> To me that's a no brainer... PR commits is the best approach... simpler to
> handle, review.. and you could even get tests working to validate the
> changes are consistent and accurate with the testsuite. It really improves
> collaboration with anyone interested in contribute code.
> However, We have a two issues to get sorted to make that work:
> I - PR builds We will need a bot user that would have push authorization on
> the mirror:
I doubt infra would be happy with a bot user having push rights to the
repo. There is a Pull Request build process (sounds like you already found
that though) leveraging the ASF Jenkins instances though. You can log in to
Jenkins with your existing committer ldap credentials, but you will need
granted rights (by the PMC chair usually) to actually configure anything on

> II - Authorization for committers to close PRs.
> We will merge PRs manually but we still need a way to close PRs when we
> reject issues.

In the past this has been ruled out, committers can request addition to the
'Apache' organization on github that the mirrors live under, but only infra
team members have the necessary rights to update anything within it. The
expectation seems to be that you either file JIRA requests with infra to
clean up stale Pull Requests, ask the person who opened it to close it, or
leverage commit messages to do so ("This closes #foo" etc) when merging to
the ASF hosted git repo.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message