I've been already using github PRs for some time now. Once you specify the 
ticket number, the comments and discussion are persisted in Apache Jira as work 
log so it can be audited if desired. However, committers usually squash and 
commit the changes once the PR is approved. We don't use the merge feature in 
github. I don't believe github we can merge the commit into multiple branches 
through the UI. We would need to merge it into one branch and then manually 
merge that commit into other branches. The big upside of using github PRs is 
that it makes collaborating a lot easier. Downside is that it makes it very 
difficult to follow along the progress in Apache Jira. The messages that github 
posts back include huge diffs and are aweful.

    On Thursday, December 13, 2018, 1:10:12 AM GMT+5:30, Benedict Elliott Smith 
<bened...@apache.org> wrote:  
 Perhaps somebody could summarise the tradeoffs?  I’m a little concerned about 
how it would work for our multi-branch workflow.  Would we open multiple PRs?

Could we easily link with external CircleCI?

It occurs to me, in JIRA proposal mode, that an extra required field for a 
permalink to GitHub for the patch would save a lot of time I spend hunting for 
a branch in the comments.

> On 12 Dec 2018, at 19:20, jay.zhu...@yahoo.com.INVALID wrote:
> It was discussed 1 year's ago: 
> https://www.mail-archive.com/dev@cassandra.apache.org/msg11810.html
> As all Apache projects are moving to gitbox: 
> https://reference.apache.org/committer/github, should we revisit that and 
> change our review/commit process to use github PR?A good example is 
> Spark:"Changes to Spark source code are proposed, reviewed and committed via 
> Github pull requests" (https://spark.apache.org/contributing.html).
> /jay

To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Reply via email to