kaliy commented on pull request #817:
URL: https://github.com/apache/avro/pull/817#issuecomment-625398849
hi, the pull request has been approved. could you please merge it?
and what about 1.9? should I backport this change to that branch as well?
I'd like a issues@avro or notifications@avro that has the detailed
messages from Github and Jira. Great suggestion.
I would prefer PR and jira issue creation / closure still go to the dev
list, but I don't feel strongly about it since I will probably subscribe to
both lists.
On Thu, May 7, 2020
Yes, I'd be in favor of having a separate ML. If you want to keep track of
the action at the repository, you can also get notified using Github.
Cheers, Fokko
Op do 7 mei 2020 om 14:37 schreef Ismaël Mejía :
> Let's wait for others opinions and if we agree I will proceed to
> create the ML next
Let's wait for others opinions and if we agree I will proceed to
create the ML next week.
On Thu, May 7, 2020 at 12:13 PM Ryan Skraba wrote:
>
> I think it's safe to create issues@ and merge the PR right away -- it
> would pretty much restore the behaviour the dev@ list had at the
> beginning of
I think it's safe to create issues@ and merge the PR right away -- it
would pretty much restore the behaviour the dev@ list had at the
beginning of the year.
I have all my mailing lists dumped into the same folder, but if
issues@ existed for JIRA and Github notifications, I would be tempted
to
