On 2/23/2019 2:50 PM, Cheryl Sabella wrote:
AM Karthikeyan wrote:
I would also recommend waiting for a core dev or someone to provide
some feedback or confirmation on even an easy issue's fix since it's
easy to propose a fix to be later rejected due to various reasons
resulting
I have done what I was asked to do: I added tests and docs in a new
PR (GH-11816) as of Feb 10.
Since that time, the API has matured thanks to thoughtful feedback
from a number of active reviewers. At present, we appear to have
stabilized around an API and code that deserves to be exercised
furt
On Fri, Feb 22, 2019 at 11:11 AM Karthikeyan wrote:
> I would also suggest cleaning up the existing set of easy issues where the
> issues was tagged as easy initially followed by discussion about how the
> though easy has other concerns like backwards compatibility due to which it
> can't be merg
