I'm excited to see progress towards a sane state for contributors to pile
on, but, in addition to Jim's point, I have a few concerns:
+ Which build is the pre-commit?  The master CI looks ~75% red:
https://travis-ci.org/apache/thrift/builds - still dauntingly red for a new
contributor imo.
+ Is the contributing advice still accurate?:
https://thrift.apache.org/docs/HowToContribute

On Mon, Jul 11, 2016 at 9:47 AM, Jim King <[email protected]> wrote:

> I suggested to Jake in an email that we should drain the pull request list
> before we do this.  There are 110+ open pull requests on github.  That size
> backlog is not healthy.  Anything recent that can be rebased and merged
> should be included.  Anything older than a couple months should probably be
> declined outright and the author may resubmit it.
>
> - Jim
>
> -----Original Message-----
> From: Aki Sukegawa [mailto:[email protected]]
> Sent: Monday, July 11, 2016 5:14 AM
> To: [email protected]
> Subject: Re: 0.10.0
>
> +1 !
>
> On Mon, Jul 11, 2016, 17:07 Jens Geyer <[email protected]> wrote:
>
> > +1
> > ________________________________
> > Von: Jake Farrell
> > Gesendet: 11.07.2016 04:02
> > An: [email protected]
> > Betreff: 0.10.0
> >
> > With the builds now solely on travis and the pre-commit green again
> > what are peoples thoughts on cutting 0.10.0, any objections?
> >
> > -Jake
> >
>
> ---------------------------------------------------------------------------------------
> PRIVACY STATEMENT:
> This message is a PRIVATE communication.  This message and all attachments
> are a private communication sent by SimpliVity and are considered to be
> confidential or protected by privilege. If you are not the intended
> recipient, you are hereby notified that any disclosure, copying,
> distribution or use of the information contained in or attached to this
> message is strictly prohibited.  Please notify the sender of the delivery
> error by replying to this message, and then delete it from your system.
>
> ---------------------------------------------------------------------------------------
>

Reply via email to