cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Russell Spitzer <russell.spit...@gmail.com>
Subject Re: Github pull requests
Date Fri, 26 Aug 2016 16:05:06 GMT
This is one of my favorite aspects of how contributions to Spark work. This
also makes it easier to have automated testing on new branches
automatically occurring.

-Russ

On Fri, Aug 26, 2016 at 8:45 AM Ben Coverston <ben.coverston@datastax.com>
wrote:

> I think it would certainly make contributing to Cassandra more
> straightforward.
>
> I'm not a committer, so I don't regularly create patches, and every time I
> do I have to search/verify that I'm doing it right.
>
> But pull requests? I make pull requests every day, and GitHub makes that
> process work the same everywhere.
>
> On Fri, Aug 26, 2016 at 9:33 AM, Jonathan Ellis <jbellis@gmail.com> wrote:
>
> > Hi all,
> >
> > Historically we've insisted that people go through the process of
> creating
> > a Jira issue and attaching a patch or linking a branch to demonstrate
> > intent-to-contribute and to make sure we have a unified record of changes
> > in Jira.
> >
> > But I understand that other Apache projects are now recognizing a github
> > pull request as intent-to-contribute [1] and some are even making github
> > the official repo, with an Apache mirror, rather than the other way
> > around.  (Maybe this is required to accept pull requests, I am not sure.)
> >
> > Should we revisit our policy here?
> >
> > [1] e.g. https://github.com/apache/spark/pulls?q=is%3Apr+is%3Aclosed
> >
> > --
> > Jonathan Ellis
> > Project Chair, Apache Cassandra
> > co-founder, http://www.datastax.com
> > @spyced
> >
>
>
>
> --
> Ben Coverston
> DataStax -- The Apache Cassandra Company
>

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