The following is also pretty low hanging fruit (one line change): https://issues.apache.org/jira/browse/AVRO-2057
—Z > On Mar 22, 2018, at 11:55 AM, Bridger Howell <[email protected]> wrote: > > Not a committer, but I'd like to chime in and say that I'd absolutely love > to see another set of official releases soon. > > When looking through the blockers in JIRA, AVRO-1810 and AVRO-1891 stand > out a bit - does anybody know if those issues should actually be considered > "blockers"? > Caveat here: I do have a personal interest in seeing AVRO-1891 fixed, and > if we do decide that it is actually a blocker, I would definitely be > willing to volunteer some time to help sort it out quickly. > > On Thu, Mar 22, 2018 at 8:55 AM, Edward Anderson <[email protected]> > wrote: > >> Hi, >> >> There have been a lot of great improvements >> <https://github.com/apache/avro/compare/release-1.8.2...master> since May >> 2017 when Avro 1.8.2 was released—241 commits from 55 different >> contributors over nearly a year. We would love to see these included in a >> new versioned release. Right now, people affected by this year's worth of >> fixes need to work around the issues or do a local build of master, both of >> which are inconvenient. The number of users affected will continue to grow >> until the next release. >> >> Do you agree that it's time for a new release? If not now, when do you >> think will be best? We wanted to check in before starting our own >> workarounds. >> >> Thanks for all your work on this great project! >> >> Best, >> >> Edward Anderson >> Software Engineer >> Doximity, Inc. >> >> On Thu, Mar 22, 2018 at 10:54 AM, <[email protected]> wrote: >> >>> Hi! This is the ezmlm program. I'm managing the >>> [email protected] mailing list. >>> >>> I'm working for my owner, who can be reached >>> at [email protected]. >>> >>> Acknowledgment: I have added the address >>> >>> [email protected] >>> >>> to the dev mailing list. >>> >>> Welcome to [email protected]! >>> >>> Please save this message so that you know the address you are >>> subscribed under, in case you later want to unsubscribe or change your >>> subscription address. >>> >>> >>> --- Administrative commands for the dev list --- >>> >>> I can handle administrative requests automatically. Please >>> do not send them to the list address! Instead, send >>> your message to the correct command address: >>> >>> To subscribe to the list, send a message to: >>> <[email protected]> >>> >>> To remove your address from the list, send a message to: >>> <[email protected]> >>> >>> Send mail to the following for info and FAQ for this list: >>> <[email protected]> >>> <[email protected]> >>> >>> Similar addresses exist for the digest list: >>> <[email protected]> >>> <[email protected]> >>> >>> To get messages 123 through 145 (a maximum of 100 per request), mail: >>> <[email protected]> >>> >>> To get an index with subject and author for messages 123-456 , mail: >>> <[email protected]> >>> >>> They are always returned as sets of 100, max 2000 per request, >>> so you'll actually get 100-499. >>> >>> To receive all messages with the same subject as message 12345, >>> send a short message to: >>> <[email protected]> >>> >>> The messages should contain one line or word of text to avoid being >>> treated as sp@m, but I will ignore their content. >>> Only the ADDRESS you send to is important. >>> >>> You can start a subscription for an alternate address, >>> for example "[email protected]", just add a hyphen and your >>> address (with '=' instead of '@') after the command word: >>> <[email protected]> >>> >>> To stop subscription for this address, mail: >>> <[email protected]> >>> >>> In both cases, I'll send a confirmation message to that address. When >>> you receive it, simply reply to it to complete your subscription. >>> >>> If despite following these instructions, you do not get the >>> desired results, please contact my owner at >>> [email protected]. Please be patient, my owner is a >>> lot slower than I am ;-) >>> >>> --- Enclosed is a copy of the request I received. >>> >>> Return-Path: <[email protected]> >>> Received: (qmail 66903 invoked by uid 99); 22 Mar 2018 14:54:27 -0000 >>> Received: from pnap-us-west-generic-nat.apache.org (HELO >>> spamd1-us-west.apache.org) (209.188.14.142) >>> by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Mar 2018 14:54:27 >>> +0000 >>> Received: from localhost (localhost [127.0.0.1]) >>> by spamd1-us-west.apache.org (ASF Mail Server at >>> spamd1-us-west.apache.org) with ESMTP id DEAA4C0075 >>> for <dev-sc.1521730404.cdcaebenfbnmffdgdbal-eanderson= >>> [email protected]>; Thu, 22 Mar 2018 14:54:26 +0000 (UTC) >>> X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org >>> X-Spam-Flag: NO >>> X-Spam-Score: 1.898 >>> X-Spam-Level: * >>> X-Spam-Status: No, score=1.898 tagged_above=-999 required=6.31 >>> tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, >>> HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, >>> RCVD_IN_MSPIKE_H2=-0.001, >>> SPF_PASS=-0.001] autolearn=disabled >>> Authentication-Results: spamd1-us-west.apache.org (amavisd-new); >>> dkim=pass (1024-bit key) header.d=doximity.com >>> Received: from mx1-lw-us.apache.org ([10.40.0.8]) >>> by localhost (spamd1-us-west.apache.org [10.40.0.7]) >>> (amavisd-new, port 10024) >>> with ESMTP id yU9_aYDuYujt >>> for <dev-sc.1521730404.cdcaebenfbnmffdgdbal-eanderson= >>> [email protected]>; >>> Thu, 22 Mar 2018 14:54:24 +0000 (UTC) >>> Received: from mail-io0-f178.google.com (mail-io0-f178.google.com >>> [209.85.223.178]) >>> by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org >> ) >>> with ESMTPS id 6C81C5F202 >>> for <dev-sc.1521730404.cdcaebenfbnmffdgdbal-eanderson= >>> [email protected]>; Thu, 22 Mar 2018 14:54:24 +0000 (UTC) >>> Received: by mail-io0-f178.google.com with SMTP id e7so11304295iof.2 >>> for <dev-sc.1521730404.cdcaebenfbnmffdgdbal-eanderson= >>> [email protected]>; Thu, 22 Mar 2018 07:54:24 -0700 (PDT) >>> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; >>> d=doximity.com; s=google; >>> h=mime-version:in-reply-to:references:from:date:message- >>> id:subject:to; >>> bh=b21Ou2nfA9LXejKny8mSEGLOuu7V4jbJybdzCeaNGRA=; >>> b=ms9pOJwbu6bXodOgItkxHmw3aYItlZw8xAHpInh5sYksRdeGFMMjUTKuaw4z >>> 1uVsMK >>> a80dEgbShulWWaE3S5UCLy9zpqWdECKcgmF+ >>> CpVzzpAyzassgfiCZmpXHFRrSh37xGXY >>> xIKb8AZnK+NC8jhQ3ODHAePx5noPgRBt0DaPU= >>> X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; >>> d=1e100.net; s=20161025; >>> h=x-gm-message-state:mime-version:in-reply-to: >> references:from:date >>> :message-id:subject:to; >>> bh=b21Ou2nfA9LXejKny8mSEGLOuu7V4jbJybdzCeaNGRA=; >>> b=PKKez7wscQiIa+0PCrzix+/tUsgQasHHQqh/ >>> emT8b8ww4JHhkjxb5ge7OPjazkKCkU >>> bf5wZiDg+JKLuOAxmncId2q0WRfp5MgJp6pSn41 >>> y6/8bse7si0hbYwt7PZLQ1R4gqnfF >>> GF81dKIvoBz43RNQNpfbs+HMzy0B2YIW5ocWYINq5JpdYuwtjHP+ >>> uae5V65ljQK7ZLYe >>> c7sVWZZwLRY9DnqoDTELyRaIb90Vmrm6oW3qlSVRuq0YaX2QZRbKomBx6y4Y >>> jcPtMK1O >>> QKI6em3eqQ2UdFZiQEkXy/JpkhU1ZA9D6myoaU3tVisDLun3z3mV >>> adMxairPbDSNSRdK >>> /oBw== >>> X-Gm-Message-State: AElRT7FBrd/2lfQUfb+F3igw2jJcTCgWsraD3NBKs0cxRE8we >>> Wiky9uH >>> o1xPHHa926skpJtNKHCKyE/KW7kVOiQG0h5nM4tmJRP5 >>> X-Google-Smtp-Source: AG47ELuLQ+fSSc9Nndrb3qygHznHsGy7Ovviji8f >>> j0nfSD/eDhiEv+ZtEaH2OPyTOBIJySvGkXvJeVxF6aoHMK3wBxE= >>> X-Received: by 10.107.141.84 with SMTP id p81mr24331006iod.97. >>> 1521730463711; >>> Thu, 22 Mar 2018 07:54:23 -0700 (PDT) >>> MIME-Version: 1.0 >>> Received: by 10.2.168.7 with HTTP; Thu, 22 Mar 2018 07:53:43 -0700 (PDT) >>> In-Reply-To: <[email protected]> >>> References: <[email protected]> >>> From: Edward Anderson <[email protected]> >>> Date: Thu, 22 Mar 2018 10:53:43 -0400 >>> Message-ID: <CAO0Eq89oOO00s2mHsz-NEvJ5ftktp8+2hujoC3v0Bfita7sCzw@mail. >>> gmail.com> >>> Subject: Re: confirm subscribe to [email protected] >>> To: dev-sc.1521730404.cdcaebenfbnmffdgdbal-eanderson=doximity.com@avro. >>> apache.org >>> Content-Type: multipart/alternative; boundary=" >>> 94eb2c061d2ebbd9f50568017bde" >>> >>> >> > > > > -- > > Bridger Howell > > Software Engineer > > 920 Front Street > > Helena, MT 59601 > > M: 406.422.9225 > > -- > > > The information contained in this email message is PRIVATE and intended > only for the personal and confidential use of the recipient named above. If > the reader of this message is not the intended recipient or an agent > responsible for delivering it to the intended recipient, you are hereby > notified that you have received this message in error and that any review, > dissemination, distribution or copying of this message is strictly > prohibited. If you have received this communication in error, please > notify us immediately by email, and delete the original message.
