I lack the background on why that odd "avro/binary" style was chosen.
Registering an IANA media type for Avro and supporting it in the different
implementations sounds like an excellent idea!
Other Apache projects have registered IANA types like
'application/vnd.apache.thrift.binary' or
'applicati
+1 to move to Java 11. Most of our downstream projects have moved out of
Java 8 and the fact that we are getting behind on our own dependencies is a
sign of the current state of the ecosystem. So good to move, and no need to
change the full version. 1.12.0 should be good.
We should probably tackle
+1 to do a release.
If we want to have a release 'soon' it is probably a good idea to not wait
for the `avro-gradle-plugin` to be included since there is still a good
amount of work to be done to get it merged, so it will end up delaying the
release.
We don't have a strict policy for new features
> > > > > > > > > is a
> > > > > > > > > > simplistic apple icon with a chunk missing. I would posit
> > > that
> > > > if
> > > > > > > Apple
> > > > > > > > > > wrote 'Apple' on their icon, it wouldn't be nearly as
> > > > ef
f time to work out the CI and PRs.
>
> All my best, Ryan
>
> On 2023/10/02 16:04:48 Ismaël Mejía wrote:
> > Hello,
> >
> > I just filled AVRO-3878 Rename default branch to be 'main'
> >
> > Many projects have moved their default git branch to use the
Hello,
I just filled AVRO-3878 Rename default branch to be 'main'
Many projects have moved their default git branch to use the name
'main' instead of 'master'. Changing Avro's default branch name is not
only important for inclusiveness and conscious language reasons, but
also because git and gith
V9.2
Like Fokko I was also not so close to the subject and it is great to
see the final selection.
It looks so great. Thanks for all the work Emma and everyone!
Ismaël
On Mon, Oct 2, 2023 at 3:23 PM Fokko Driesprong wrote:
>
> Hey Oscar,
>
> Thanks for raising this vote. I wasn't active in the
+1 (binding)
I struggled a lot to do a full build with the docker image, we should
probably improve some things there. Apart of this all the rest looked
good, sigs/shas ok I mostly tested in detail the Java bits.
Ismaël
On Tue, Sep 19, 2023 at 5:37 PM Fokko Driesprong wrote:
>
> Thanks for runn
+1 a pity we have to do this so close to each other but it is probably good
timing to catch up also downstream.
Thanks Ryan for leading this too !
On Wed, Jul 12, 2023 at 2:50 PM Niels Basjes wrote:
> Yes, +1 from me for having a regression release.
>
> In my opinion this regression fix should
+1
Verified signatures
Full build and test of Java
Full build and test of all packages with the docker image
Validated API compatibility (only one new method added for core)
Validated downstreaming on both Parquet and Spark
All good to go!
We should add the description to the github release, (I a
+1 (binding)
I made my mind about this, better to have it than not and worse case
if it gets unmaintained or makes things too complex we can always
decide if remove it.
Regards,
Ismaël
On Wed, Oct 12, 2022 at 12:39 PM Oscar Westra van Holthe - Kind
wrote:
>
> +1 (non-binding) from me
>
> FYI:
>
Hi,
I want to add some comments here to not hijack the VOTE thread.
I have mixed feelings about this. I like the idea of the Avro
community maintaining the plugin specially if it is going to go
unmantained, it can definitely grow because of it, but I am afraid of
two things:
1. Would it be just
> > the vote has passed to release Avro 1.11.1.
> > >
> > > I will start releasing artifacts to the various package managers and
> > > send the announcement within the week.
> > >
> > > Jack, I'll be sure to add to the release anouncement -- i
+1
Checked checksums + Fully build all passed (via docker on x64)
Tested downstreaming in Parquet and Spark all looks good
On Fri, Jul 29, 2022 at 8:49 AM Martin Grigorov wrote:
>
> On Fri, Jul 29, 2022 at 3:08 AM Jack Klamer wrote:
>
> > I believe the derive proc macro for rust is included in
Hello Nilesh,
The Avro project makes around 2-3 releases per year since 2019 (when
we got a new release pace). Next release will be 1.11.1 (the link
Martin referred), it should be happening hopefully soon, your
contribution will be part of it.
We tend to cherry-pick as much as we can so patch rel
+1 for going ahead. Most pending merges are improvements than seem not blocking.
Thanks Ryan for all your work to make this happen!
On Mon, Jul 25, 2022 at 9:52 PM Martin Grigorov wrote:
>
> Hi,
>
> +1 for option 1.
>
> IMO we should make releases more often instead of postponing the releases
>
Hello,
ApacheCon North America is back in person this year in October.
https://apachecon.com/acna2022/
Together with Jarek Potiuk, we are organizing for the first time a Data
Engineering Track as part of ApacheCon.
You might be wondering why a different track if we already have the Big Data
trac
Wow this is pretty neat ! Nice job Martin! A modern website can
encourage more contributions.
I am more interested on content than aesthetics first. Is everything
already migrated? Anything missing? Any issue to report?
On Tue, Nov 2, 2021 at 7:01 PM Martin Grigorov wrote:
>
> Hi,
>
> Anyone wil
+dev@avro.apache.org
Hello,
Adding dev@avro for awareness.
Thanks Jorge for exploring/reporting this. This is an exciting
development. I am not aware of any work in the Avro side on
optimizations of in-memory representation, so any improvements there
could be great. (The comment by Micah about b
+1 (binding)
Run Java full build, Let's ship it!
Ismaël
On Tue, Oct 26, 2021 at 6:32 PM Daniel Kulp wrote:
>
>
> +1 - Thanks for driving this forward!
>
>
> Dan
>
>
>
>
> > On Oct 21, 2021, at 6:21 AM, Ryan Skraba wrote:
> >
> > Hi everyone,
> >
> > I'd like to propose the following RC2 to be
Hello,
You will find here the Avro report for this quarter, let me know if
any comments or ideas to improve it or to improve future versions.
## Description:
Apache Avro is a data serialization system with a compact binary format. It is
used for storing and transporting schema driven serialized
Oh I missed this one. Congratulations David, well deserved !
On Tue, Oct 5, 2021 at 2:50 PM Martin Grigorov wrote:
>
> Congratulations. David!
>
> On Tue, Oct 5, 2021 at 3:28 PM Ryan Skraba wrote:
>
> > The Project Management Committee (PMC) for Apache Avro
> > has invited David Mollitor to bec
Hello,
You will find here the Avro report for this quarter, let me know if
any comments or ideas to improve it or to improve future versions.
## Description:
Apache Avro is a data serialization system with a compact binary format. It is
used for storing and transporting schema driven serialized
I finally went ahead and merged the Avro rust PR that imports the code
from `avro-rs` and adapts it into the project structure of Apache
Avro.
There are some minor clean-ups to do, I filled an issue for this
https://issues.apache.org/jira/browse/AVRO-3157 and I expect to work
on the following days
I'm happy to announce that we have unanimously approved to accept the
donation of avro-rs as the Apache Avro Rust implementation.
There are 6 approving votes, 4 of which are binding:
* Fokko Driesprong
* Ryan Blue
* Ryan Skraba
* Ismaël Mejía
There are no disapproving votes.
Thanks everyon
Dear all,
The developers of
https://github.com/flavray/avro-rs/
have been in touch with some members of the Apache Avro Project Management
Committee (PMC). Based on these discussions, it is being proposed to donate
this
Avro Rust implementation into the Apache Avro project to continue
developing
For awareness Github Actions requires now to approve the CI runs for new
contributors, so this is a call for committers to pay attention to this and
help when they see new users PRs so they don't stay just waiting without
running.
https://github.blog/changelog/2021-04-22-github-actions-maintainers
+1 Sounds really nice to have.
On Fri, May 14, 2021 at 8:51 PM Michael Smith wrote:
> We recently started using GitHub CodeQL (formerly Semmle) at work, and as a
> multilanguage code and security scanning tool I have found it quite useful
> and informative. IIUC, it's free for open source projec
Hello,
You will find here the Avro report for this quarter, let me know if
any comments or ideas to improve it or to improve future versions.
-
## Description:
Apache Avro is a data serialization system with a compact binary format. It is
used for storing and transporting schema driven seri
Great news!
Thanks a lot Ryan for all your work as release manager !
On Wed, Mar 17, 2021 at 3:03 PM Ryan Skraba wrote:
>
> The Apache Avro community is pleased to announce the release of Avro 1.10.2!
>
> All signed release artifacts, signatures and verification instructions can
> be found here:
+1 (binding)
Validated signatures and hashes
Built distribution from source for Java
Tried with downstream projects (Spark/Parquet) with success
On Thu, Mar 11, 2021 at 7:09 PM Daniel Kulp wrote:
>
>
> +1
>
> Most of my testing was with RC1, but some followup with RC2 doesn’t reveal
> anything
Thanks for bringing this subject Michael, we have vastly improved our
communication with downstream projects (Spark/Parquet/Hive) and most
of the issues you and other users have had will be available soon in
upcoming versions of those projects.
Spark finally merged the upgrade to Avro 1.10.1 recen
Thanks Ryan ! Go RC2 Go !
On Tue, Mar 9, 2021 at 6:19 PM Ryan Skraba wrote:
>
> Hello everyone! I've been testing the RC1 in a lot of our internal code,
> and a colleague brought up a potential high-priority CVE with that has been
> fixed in Velocity 2.3.
>
> Looking at the recent Velocity chang
BIg +1 Ryan,
It definitely makes sense to have this release and is consistent with
what we have been doing in the last versions.
We should ideally also catch some dependency upgrades for the
javascript implementation if there is anyone with the expertise who
wants to contribute to this it will be
That's excellent news!
I was just wondering which version of C++ should we target?
Also what are the consequences for our users? I mean do you plan to
keep a backwards compatible public API so users of an older version
can still be able to link with it, or do you plan to use 'new C++
features' th
e in particular requires probably to sync the
dependency updates because of conflicts between dependencies.
On Mon, Jan 4, 2021 at 11:59 AM Ismaël Mejía wrote:
>
> We enabled recently dependabot to automate dependency upgrades [1]. Results so
> far seem good including having new CVEs alerts!
>
in what python versions to track, and for dropping
> lang/py3 in the next release.
>
>
>
>
>
> On Thu, Jan 21, 2021 at 09:14 Ismaël Mejía wrote:
>
> > Michael Can we close this vote?
> > It seems we have consensus (and if you vote the minimum 3 +1).
> >
> >
Michael Can we close this vote?
It seems we have consensus (and if you vote the minimum 3 +1).
There is one extra open question should we proceed and get rid of
lang/py3 on master, and go straight to Avro 1.11.0 as our next
release?
On Thu, Jan 7, 2021 at 5:45 PM Ismaël Mejía wrote:
>
>
thon "until its usage on PyPI
> > falls below 5%", which we can see by drilling down at
> > https://pypistats.org/packages/pip.
> >
> >
> > Voting:
> >
> > The voting process is here:
> > https://www.apache.org/foundation/voting.html. Th
We enabled recently dependabot to automate dependency upgrades [1]. Results so
far seem good including having new CVEs alerts!
Maybe we could automate further by auto merging the PRs given some conditions
like a whitelist of dependencies that are now stable enough and when tests are
green we shall
for JIRA, but I suspect that it will not happen.
>
> [1] https://cwiki.apache.org/confluence/display/AVRO/How+To+Release
>
> On Mon, Jan 4, 2021 at 9:50 AM Ismaël Mejía wrote:
>
> > So far we have not discussed yet the next release date/version but I
> > will expect i
+1 good idea! Can you please open the vote Michael
Do we have multiple-python version tests? I suppose this will be
easier to do now with the move to github actions!
On Fri, Dec 18, 2020 at 5:40 PM Michael A. Smith wrote:
>
> I propose that we track pip, the official Python package installer, in
Excellent work / idea / development. 2021 starting great !
I really like the idea of devs not having to wait for the all
languages build to have feedback earlier, but we probably need an
extra action for interop tests and that should match the supported
languages.
We still need to discuss two mor
+1 A big late to vote given it is already merged :P
But excellent to have this, great work
On Tue, Dec 29, 2020 at 1:34 PM Tim Perkins wrote:
>
> +1 from me -- this should make it easier for contributors and make the
> build more stable!
>
> On Mon, Dec 28, 2020 at 4:18 PM Driesprong, Fokko
> w
So far we have not discussed yet the next release date/version but I
will expect it to be 1.10.2.
Do you have any particular reason to produce a release quicker than
the ongoing average 6 months pace?
On Mon, Dec 21, 2020 at 3:14 AM Michael A. Smith wrote:
>
> The commit log for branch-1.10 says
+1
Validated signatures and run full docker tests.
Build and tested Java deps code on downstream projects without further issues.
Great work Ryan!
On Wed, Nov 25, 2020 at 7:51 PM Daniel Kulp wrote:
>
> +1
>
>
> Did some testing with various things with the Java stuff on my Mac.
>
> Also did a
Dependabot is enabled now, time to validate all these upgrades.
The more eyes we can have the better !
Notice that these upgrades won't be taken for the ongoing release (1.10.1)
but probably catched up and eventually backported for future ones.
On Fri, Nov 13, 2020 at 3:12 PM Ismaël Mejía
"Automate python
> formatting" that touched on dependabot. At the time, Fokko, and you,
> Ismaël, were discussing that dependabot might violate Apache rules about
> modifying the code. Has that been worked out?
>
> I'm otherwise totally in favor of this.
>
> On Fri,
Hi everyone,
Github has a bot to create Dependency Update PRs and report security issues
called dependabot. I requested INFRA to enable it for Avro so we can benefit of
more automation. I am enthusiastic in particular about the multiple language
support (so far we can get automatic updates for Jav
Krishnan You can take a look at
https://cwiki.apache.org/confluence/display/AVRO/How+To+Release For steps that
could help to reproduce the build.
A really important contribution is to try to update in any of the projects where
you use Avro to use the latest version (the one being voted) and report
Ryan, thanks for volunteering, it is perfect timing to keep the release pace. So
big +1
Do you have a proposition or a possible date to cut the branch so we can decide
what ongoing things may make it (or not).
On Wed, Oct 14, 2020 at 11:16 AM Ryan Skraba wrote:
>
> Hello, great timing!
>
> I'd d
Oups I found I ended up somehow archiving this thread before answering.
Congratulations Ryan, well deserved !
Thanks a lot for all the work and great attitude that you have brought to
the community!
On Fri, Sep 18, 2020 at 2:12 PM Ryan Skraba wrote:
> Many thanks to everyone! It's been a super
The Apache Avro community is pleased to announce the release of Avro 1.10.0!
All signed release artifacts, signatures and verification instructions can be
found here: https://avro.apache.org/releases.html
This release includes 189 Jira issues, including some interesting features:
C#: AVRO-2389 A
nstalled and tested with the following Ruby projects:
> - avro-builder
> - avro_turf
> - avromatic
> - avro-resolution_canonical_form
>
> On Mon, Jun 22, 2020 at 11:43 AM Ismaël Mejía wrote:
>
> > Hi everyone,
> >
> > I'd like to propose the fol
+1 (binding)
Run full build in all languages, validated signatures
Tried with personal downstream project
Validated binary compatibility nothing unexpected
On Fri, Jun 26, 2020 at 6:32 PM Ismaël Mejía wrote:
>
> Sean I want to confirm that the link you mention is the correct staging rep
irmed that the avro-maven-plugin pom has an up to date
> > plexus-utils dependency.
> > * A brief inspection of the docs looks good.
> >
> > a compatibility report for the java libraries would be nice to have,
> > but I do not have the free time to come up with one c
Oups there was a mistake in the previous email. I forgot to update the vote
end date.
Given sufficient votes, I would like to close it on Thursday
, June 25th, 2020 when the 72h has passed.
Thanks to Anders Sundelin for noticing
On Mon, Jun 22, 2020, 5:42 PM Ismaël Mejía wrote:
> Hi every
ke to close after noon UTC
Friday, June 12th, 2020
[ ] +1 Release this as Apache Avro 1.10.0
[ ] +0
[ ] -1 Do not release this because...
Best regards,
Ismaël Mejía
On Tue, Jun 16, 2020 at 6:29 PM Ismaël Mejía wrote:
>
> Kind reminder, We have so far 2 PMCs +1
>
> Please vote, help us with testing and validation in particular in less
> maintained languages.
>
>
>
> On Mon, Jun 15, 2020 at 9:50 AM Ryan Skraba wrote:
> >
&g
ting an unknown field throws an exception). In
> > > > > > practice, it's not going to impact us in the short term, since it's
> > > > > > all run on a cluster where the avro version is provided (and usually
> > > >
ve verified the signatures and SHA512 of the artifacts, so that's good!
> >
> > All my best, Ryan
> >
> >
> >
> >
> >
> >
> > On Wed, Jun 10, 2020 at 8:53 AM Anh Le wrote:
> > >
> > > Hi,
> > >
> > > H
ke to close after noon UTC
Friday, June 12th, 2020
[ ] +1 Release this as Apache Avro 1.10.0
[ ] +0
[ ] -1 Do not release this because...
Best regards,
Ismaël Mejía
)%20AND%20fixVersion%20%3D%201.10.0
Regards,
Ismaël Mejía
On Thu, May 14, 2020 at 8:42 AM Driesprong, Fokko wrote:
>
> Sounds good Ismaël, thanks for the update.
>
> We need to update the jetty which contains a CVE before cutting 1.10
>
> Cheers, Fokko
>
> Op
ou 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 week.
> > >
> > >
te to ping me (hopefully) in
advance if you want to discuss any release specific issue.
Regards,
Ismaël
On Tue, Apr 28, 2020 at 10:02 AM Ismaël Mejía wrote:
>
> Hello everyone,
>
> As discussed previously [1] we intend to do the Avro 1.10.0 release on
> May so I wanted to propose t
elopers have
> their email filters set up for various projects! It's easy to get
> overwhelmed by the volume (especially if you don't keep up daily, I
> was off most of March/April).
>
> In any case, https://github.com/apache/avro/pull/873 LGTM!
>
> Ryan
>
, May 6, 2020 at 11:47 PM Ismaël Mejía wrote:
>
> The issues in the yaml file are every comment done on every issue or
> pull requests on github (notice that the issues part probably won't
> apply to us since we use JIRA to track issues).
>
> Currently we receive ALL JIRA not
t; > Yep, I think it's a little bit noisy for our mailing list with such
> > notifications. But it's fun to see what other people are working on.
> >
> > IMHO, in addition to a new mailing list, we should have a better label
> > mechanism for easily routing/filt
ons to be similar to one another over being
> > > > idiomatic in their own language, and we can't do a release for just one
> > > > language. If boiling down the project into a single core lib for
> > multiple
> > > > languages is what it takes to fix
Hello,
Some of you have probably noticed that we are receiving a LOT of extra
notifications that were not active in the past. This is happening because
Apache INFRA installed a new way to map notifications into mailing lists for its
projects and the default configuration right now is sending all
Thanks Andy for pointing this out. It is important that we are more responsive
to contributors. I have my good dose of mea culpa on this recently but please do
not forget that even if Avro is a crucial piece of the Big Data ecosystem, at
this point there is not a single person up to my knowledge wh
Hello everyone,
As discussed previously [1] we intend to do the Avro 1.10.0 release on
May so I wanted to propose to cut the branch the next May 15th. The
idea is that in the following weeks we work hard on reviews and issue
triage and maybe the latest dependency updates. Once the branch is cut
we
Huge +1 to recover the Avro Enhancement Proposals (AEP)
The experimental features Ryan mentioned definitely merit(ed) to be
part of it, and in particular the procedure to decide when they will
become ‘stable’ or default, for example for fastread. Also other
proposals/discussions like the split rel
Bringing my comment from the JIRA ticket here for discussion:
> "One argument against semantic versioning is the fact that Avro supports
9 language APIs, so if let's say C++ breaks its backwards compatibility
should we move the version number up for every single language? Sounds like
a burden and
park? I would like
> to try to apply it on top of
>
> https://github.com/apache/spark/pull/26804 <
> https://github.com/apache/spark/pull/26804>
>
> which attempts to upgrade the Parquet dependency for Spark to 1.11.0.
>
> Thank you,
>
> michael
>
>
>
Ah lovely question.
tldr; version
Spark depends on Hive so Hive should be upgraded first
Spark depends on two versions of Hive a fork by Spark of 1.x and upstream
Hive 2.x
Upgrading the first is not even discussed at the moment, for the second I
added a patch that passes all tests if you run it ag
Now that Avro 1.9.2 was released I wanted to propose a sort of roadmap for
the
next release. We already have accumulated a good chunk of new features and
fixes
that can be released as Avro 1.10.0. I would like to propose that we cut
the
1.10.x branch in may 2020 to have a 'major' release exactly o
I don't think we should stop the release because of that since all the
artifacts
are available and still can be tested without docker.
We should definitely for the future try to pin the OS docker image so this
don't
happen again to a stable version and maybe get the exact Java related JDK
and
tool
+1 (binding)
- Validated signatures for src/doc
- Build Java version for source, all tests passing
- Compared backwards compatibility with 1.9.1
https://gateway.pinata.cloud/ipfs/QmbQqR63ZEKWTvAG6jBQMr1AUBkMdu67LdbUWHMSDZ2GMy
- Validated installed artifacts to upgrade parquet-mr, everything smooth
Can we please also cherry pick these two now that we'll have an RC2.
AVRO-2726: Upgrade Jackson to version 2.10.2 #799
AVRO-2727: Update hadoop3 to version 3.2.1 #800
Thanks
On Thu, Feb 6, 2020 at 4:17 PM Driesprong, Fokko
wrote:
> Thanks Ryan for taking care of this.
>
> Unfortunately, I have t
+1
Having experimental features backported sounds good to enable early testing
and
feedback, only condition should be not breaking backwards compatibility.
Probably worth to mention in the release notes and to create a JIRA + PR to
enable this as the default behavior for 1.10. We have to pay atte
>
> On Sun, Sep 8, 2019, 11:52 AM Ismaël Mejía wrote:
>>
>> Hello,
>>
>> Next week Apachecon US 2019 is happening. I know that at least two
>> other members of the Avro community will be around so I was wondering
>> if there might be others around who could
Hello,
Next week Apachecon US 2019 is happening. I know that at least two
other members of the Avro community will be around so I was wondering
if there might be others around who could be interested in a
get-together to meet each other and discuss about Avro or just for
fun.
Regards,
Ismaël
Congrats Nándor, well deserved!
On Sat, Aug 31, 2019 at 10:30 AM Driesprong, Fokko
wrote:
> Welcome Nándor, great to have you on the PMC! 👍
>
> Op za 31 aug. 2019 om 09:20 schreef Niels Basjes :
>
> > Welcome!
> >
> > On Fri, Aug 30, 2019, 23:39 Brian Lachniet wrote:
> >
> > > Congratulations,
Hello,
I would like to bring the attention to
https://issues.apache.org/jira/browse/AVRO-2531
They discovered a CVE that allows to do a DoS via commons-compress.
Due that this is a 'core' dependency for us. I think we should
probably do an extra RC to include this one.
WDYT?
On Wed, Aug 28, 201
is only the performance tests
> and no core components of Avro. The impact will be minimal and I would like
> to keep it Java11 compatible.
>
> It would be nice to introduce some check to capture this in the future.
>
> Cheers, Fokko
>
> Op wo 21 aug. 2019 om 16:52 schreef Ismaël Me
Hello,
I have a question, while checking some Java 11 improvements I
discovered that the Perf module that we introduced in 1.9.0 has a
split package issue that can cause conflicts with Java 11. I was
wondering if we could fix this (the fix is just to isolate the module
classes into its own package
for this:
> >
> > https://issues.apache.org/jira/browse/AVRO-1852
> >
> > Doug
> >
> > On Mon, Jul 15, 2019 at 6:49 AM Ismaël Mejía wrote:
> >
> > > +dev@avro.apache.org
> > >
> > > On Mon, Jul 15, 2019 at 3:30 PM Ryan Skraba w
+dev@avro.apache.org
On Mon, Jul 15, 2019 at 3:30 PM Ryan Skraba wrote:
>
> Hello!
>
> I'm looking for any discussion or reference why the Schema object isn't
> serializable -- I'm pretty sure this must have already been discussed (but
> the keywords +avro +serializable +schema have MANY result
Probably is a good idea that we publish our policy around python
support [1] as other projects have done [2].
I think supporting python 2 makes sense at least for our latest
release of this year so probably 1.9.x or eventually 1.10.x.
I am not at all familiar with our python3 codebase, are we feat
ed
> > > <https://dependabot.com/blog/hello-github/> by Github, so I guess we can
> > > ask Github to sign a CLA :-) It is worth a shot of discussing this
> > upstream
> > > in the ASF. Dependabot letting us know when there is a library with known
> > &g
+1 for Black, great idea and in line we the changes we did with
spotless for the Java code base.
About dependabot I think this is an interesting case to discuss in
upstream apache lists. So far ASF allows bots that do not touch the
code, for example for metadata, as we do with the autolabeler bot.
For info it seems that mvnrepository has finally catched up.
https://mvnrepository.com/artifact/org.apache.avro/avro/1.9.0
On Tue, May 21, 2019 at 5:51 PM Ismaël Mejía wrote:
>
> Thanks for fixing that Fokko.
> Maven Repository always takes 'ages' to catch up but since
t; Cheers, Fokko Driesprong
>
> Op di 21 mei 2019 om 10:06 schreef Ismaël Mejía :
>
> > Seems the jars are now everywhere. Are we going to do an Announcement
> > (specially to announcement mailing list)?
> > Also the download link points still to both 1.8.2 and
ppears to have been
> > > > published
> > > > > > 5/8
> > > > > > (the same day as RC4 was announced but ~1week before vote passed).
> > > > > >
> > > > > > Is this the release build (presumably the same as RC4) or an
This is a fork of the discussion started in the release vote thread [1].
Just to keep the discussion going and follow up on issues and projects
that deserve attention.
So far open issues are:
BEAM-7328 Update Avro to version 1.9.0 in Java SDK
HIVE-21737 Upgrade Avro to version 1.9.0
FLINK-12532 U
Yes, sorry for polluting this thread, will fork it.
On Thu, May 16, 2019 at 1:45 PM Sean Busbey wrote:
>
> The matter of upgrading downstream projects should get its own thread
> on dev@avro rather than occurring on this VOTE.
>
> On Thu, May 16, 2019 at 5:14 AM Ismaël Mejía wrot
ted and removed Avro methods (related to
> > Jackson removal from public API).
> >
> > On Wed, May 15, 2019 at 11:04 PM Ismaël Mejía wrote:
> >
> > > Getting a new release of Avro feels amazing, thanks a lot Fokko for
> > > all your wokr to get this out with
somewhere in
> > MANIFEST.MF?
> >
> > jacob
> >
> > On Tue, May 14, 2019 at 1:04 PM Driesprong, Fokko
> > wrote:
> >
> > > Thank you all,
> > >
> > > I'm happy to announce, the vote for Avro 1.9.0 has passed.
> >
+1 (non-binding)
Validated checksums and signatures
Installed locally via `mvn clean isntall` and run Java tests.
Little reminder for people in the PMC, so far we don't have enough
binding votes to get it out.
On Thu, May 9, 2019 at 2:07 PM Daniel Kulp wrote:
>
> +1
>
> Dan
>
>
> > On May 8, 2
1 - 100 of 112 matches
Mail list logo
