Hi all, Like AVRO-2250 for 1.9.0 release I created a ticket AVRO-2273 for tracking release 1.8.3. To get a sense of what needs to be done for the releases, I request all of you to mark the "release version" in those JIRA tickets that you'd like to be resolved. As of now, there are 43 unresolved issues marked with release version 1.9.0 of which 22 are unassigned and 12 unresolved (7 unassigned) with version 1.8.3. Needless to say, if you are willing to resolve any of them, assign to yourself and possibly set the "due date" field.
Once we have the list, we can assign the unassigned one to one of us, who can resolve it or argue why an issue need not/should not be fixed. Is there anyone volunteering to be the release manager? Please assign one of these release tickets to yourself. Thank you Thiru On Wednesday, 21 November, 2018, 10:46:05 PM IST, Evan McQuinn (JIRA) <[email protected]> wrote: [ https://issues.apache.org/jira/browse/AVRO-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16694964#comment-16694964 ] Evan McQuinn commented on AVRO-2250: ------------------------------------ Hello there - I'm a colleague of [~ajakz]'s and just wanted to clarify that the issue we're interested in specifically is AVRO-2265. We're worried that we'll be blocked from going to production with v1.8.2 because of [the vulnerability in Guava|https://nvd.nist.gov/vuln/detail/CVE-2018-10237] that was discovered earlier this year. I definitely understand that you've got a backlog to work through for a 1.9 release, but maybe a smaller 1.8.3 release makes sense to address this security issue? Regardless, thanks for the work! > Release 1.9.0 > ------------- > > Key: AVRO-2250 > URL: https://issues.apache.org/jira/browse/AVRO-2250 > Project: Apache Avro > Issue Type: Task > Reporter: Nandor Kollar > Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
