Community over Code EU 2024: The countdown has started!

[Note: You're receiving this email because you are subscribed to one or more project dev@ mailing lists at the Apache Software Foundation.] We are very close to Community Over Code EU -- check out the amazing program and the special discounts that we have for you. Special discounts You still

Re: Drop support for pypy3.7 and 3.8

+1 for me! Thanks! On Tue, Apr 16, 2024 at 6:43 AM Martin Grigorov wrote: > > +1 > > On Tue, 16 Apr 2024 at 5:14, Michael A. Smith wrote: > > > Please note I'm not proposing any changes to our CPython support in > > this thread. This is just about pypy. > > > > The currently active versions of

[jira] [Created] (AVRO-3973) [Build] py3.8 and py3.9 fail with ModuleNotFoundError

Ryan Skraba created AVRO-3973: - Summary: [Build] py3.8 and py3.9 fail with ModuleNotFoundError Key: AVRO-3973 URL: https://issues.apache.org/jira/browse/AVRO-3973 Project: Apache Avro Issue Type

[jira] [Created] (AVRO-3972) [Build] pypy3.8 fails with 'Buffer' object is not iterable

Ryan Skraba created AVRO-3972: - Summary: [Build] pypy3.8 fails with 'Buffer' object is not iterable Key: AVRO-3972 URL: https://issues.apache.org/jira/browse/AVRO-3972 Project: Apache Avro Issue

[jira] [Created] (AVRO-3971) [Build] PHP failing on ubertool build.

Ryan Skraba created AVRO-3971: - Summary: [Build] PHP failing on ubertool build. Key: AVRO-3971 URL: https://issues.apache.org/jira/browse/AVRO-3971 Project: Apache Avro Issue Type: Bug

Re: [PROPOSAL] Apache Avro 1.11.4 release

Hello everyone! I've been away for a bit, but I also think a new release would be welcome :D I'm willing to put in the work to do the packaging and deployment, especially if I can help another future "release manager" get everything in place to do the next one! Are we aligned on doing a 1.11.4

Community over Code EU 2024: Start planning your trip!

[Note: You're receiving this email because you are subscribed to one or more project dev@ mailing lists at the Apache Software Foundation.] Dear community, We hope you are doing great, are you ready for Community Over Code EU? Check out the featured sessions, get your tickets with special

Re: Media Type

This sounds like an issue just waiting for someone to be sufficiently irked! Is there any reason NOT to use the common pattern? I really haven't run across any use cases that use the media type at all! All my best, Ryan On Mon, Jan 8, 2024 at 6:58 PM Ismaël Mejía wrote: > I lack the

Meet our keynote speakers and register to Community Over Code EU!

[Note: You're receiving this email because you are subscribed to one or more project dev@ mailing lists at the Apache Software Foundation.] * Merge with the ASF EUniverse!The registration for

Re: [DISCUSS] Apache Avro 1.12.0

Hey -- I think a 1.12.0 is a great idea! There's two things I'd love to see included, but aren't finished... 1. I would **love** to get the avro-gradle-plugin donation rolling so it would be off the plate of the current maintainer (and donator). 2. It's really irritating that we don't have a

[LAZY][VOTE] Nanosecond datetime support

Hey Fokko, I've edited the subject of this mail and it's now a lazy consensus :D This is probably the right way to go even if it looks like we have a de facto consensus on the PR and JIRA. We're of course welcome to continue the discussion, recap, object or approve here on the mailing list! And

Re: [VOTE] New Avro logo (final)

note, I'd also like to use the final logo as plugin icon and > > as (part of the) file icon in the JetBrains Pugin I maintain. Are there any > > objections to that? > > > > > > Kind regards, > > Oscar > > > > -- > > Oscar Westra van Hol

Call for Presentations now open: Community over Code EU 2024

form for showcasing high-level projects and incubator initiatives in a visually engaging manner. We believe this will foster lively discussions and facilitate networking opportunities among participants. All my best, and thanks so much for your participation, Ryan Skraba (on behalf of the pro

[LAZY][VOTE] Java build insights on ge.apache.org

Hello! We have a PR to integrate our builds with the ASF instance of Develocity (previously known as Gradle Enterprise). This PR adds an extension to the pom.xml file. This is automatically deactivated if you don't have a valid GRADLE_ENTERPRISE_ACCESS_KEY in your environment. In other words,

Re: [VOTE] New Avro logo (final)

e Airflow), and I can also do that if we'd like. > > Please let me know your thoughts, in the meantime, I'll start getting to > work on either creating the alternate font options for another vote or the > final format versions :D > > All my best, > Emma > > On Tue, Oct 2

Re: [VOTE] New Avro logo (final)

s a > > finalist > > > >> (the pigeon with the outlines), my mistake! > > > >> The finalists are V9.2 (or V11.2 if you prefer upwards) and V3.1 > > > >> Apologies for the confusion! > > > >> > > > >> All the be

Re: [VOTE] New Avro logo (final)

outlines), my mistake! > > > > The finalists are V9.2 (or V11.2 if you prefer upwards) and V3.1 > > > > Apologies for the confusion! > > > > > > > > All the best, > > > > Emma > > > > > > > > > > > > On Fri, Oct 20, 2023 at

Re: [VOTE] New Avro logo (final)

> > > > > > > That's my 2¢ anyways! I'm happy to make more adjustments to the fonts > > > and > > > > > the angles of the icons as we see fit, and I'm so excited to see > > which > > > > > design will be the final winner in the end! :D > > > > > > >

Re: [VOTE] New Avro logo

different from any send icon, so it cannot be > conflated > > with a message protocol icon. > > > > My vote is for V3.1 > > > > > > Kind regards, > > Oscar > > > > -- > > ✉️ Oscar Westra van Holthe - Kind > >  https://github.

Re: Rename default branch to be 'main'

Thanks for putting in this work, Ismaël! We just did a release, so we have a bit of 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

Re: [VOTE] New Avro logo

I can't stop changing my mind, but I'm going to go with V9.2 -- I really like the pigeon too, but I think the paper plane fits too nicely to pass up! Excellent work, Emma, and thanks Oscar for calling the vote. I think your voting proposal makes sense! Ryan On Mon, Oct 2, 2023 at 3:59 PM

[ANNOUNCE] Apache Avro 1.11.3 released

The Apache Avro community is pleased to announce the release of Avro 1.11.3! All signed release artifacts, signatures and verification instructions can be found here: https://avro.apache.org/releases.html This is a minor release, specifically addressing known issues with the 1.11.2 release, but

[jira] [Created] (AVRO-3873) [Build][Java] use an avro.version property to help releases

Ryan Skraba created AVRO-3873: - Summary: [Build][Java] use an avro.version property to help releases Key: AVRO-3873 URL: https://issues.apache.org/jira/browse/AVRO-3873 Project: Apache Avro

[jira] [Created] (AVRO-3872) [Build][C#] Warning on nuget upload about README

Ryan Skraba created AVRO-3872: - Summary: [Build][C#] Warning on nuget upload about README Key: AVRO-3872 URL: https://issues.apache.org/jira/browse/AVRO-3872 Project: Apache Avro Issue Type: New

Re: [DISCUSS] Release maintenance and lifecycle

car Westra van Holthe - Kind wrote: > > On fr 22 sep. 2023 18:40, Ryan Skraba wrote: > > > Back to this topic :D After a couple of extra releases on the > > branch-1.11, how do we feel about supporting two major releases? Have > > committers found it a pain in the bu

Re: [DISCUSS] Release maintenance and lifecycle

nt to split that? (I'd like to keep them bundled). > > > > "bundled" is easier for the release manager (I guess) and also for > generating the documentation. > I am fine with both approaches. > > > > > > > > > Kind regards, > > Oscar >

Avro at Community over Code 2023?

Hey -- just a quick roll call :D There are just a few talks that mention Avro in the program at Community over Code in Halifax this year.[1] If anybody is going to be there and feels like having an Avro lunch, please do get in touch! We seldom have opportunities to meet, and even if it isn't

[VOTE][RESULT] Release Apache Avro 1.11.3 RC1

Hello everyone, With eight +1 (five binding) and no 0 or -1, I'm please to announce that the vote has passed to release Avro 1.11.3. I will start releasing artifacts to the various package managers and send the announcement within the week. Thanks everyone for your contributions! Ryan Skraba

[ANNOUNCE] New committer: Christophe Le Saec

The Project Management Committee (PMC) for Apache Avro has invited Christophe Le Saec to become a committer and we are pleased to announce that he has accepted. Christophe definitely puts in the work and, has an impressive breadth of knowledge about the languages of the Avro SDK! As an ASF

[ANNOUNCE] New committer: Oscar Westra van Holthe - Kind

The Project Management Committee (PMC) for Apache Avro has invited Oscar Westra van Holthe - Kind to become a committer and we are pleased to announce that he has accepted. Oscar has done some really solid work on the IDL and JavaCC parts of the Java SDK. We trust his work and think it's of

[ANNOUNCE] New PMC member: Michael A. Smith

The Project Management Committee (PMC) for Apache Avro has invited Michael A. Smith to the PMC and we are pleased to announce that he has accepted. A PMC member helps manage and guide the direction of the project. Notably, Michael has taken a leadership role in ensuring the quality of the Python

[jira] [Created] (AVRO-3865) [Build][perl] Files are leftover after a build

Ryan Skraba created AVRO-3865: - Summary: [Build][perl] Files are leftover after a build Key: AVRO-3865 URL: https://issues.apache.org/jira/browse/AVRO-3865 Project: Apache Avro Issue Type: Bug

Re: New Big Decimal Logical type

Hello! There's a couple things going on, but I think this new type needs to be better specified in in the documentation before merging! Specifically, how are the bytes constructed and why was this representation chosen? Is there a better, more neutral represention where the underlying type

[jira] [Created] (AVRO-3864) [Build] Do a better clean based on the .gitignore file

Ryan Skraba created AVRO-3864: - Summary: [Build] Do a better clean based on the .gitignore file Key: AVRO-3864 URL: https://issues.apache.org/jira/browse/AVRO-3864 Project: Apache Avro Issue

[jira] [Created] (AVRO-3861) [Build] Add RAT exclusions for python docs

Ryan Skraba created AVRO-3861: - Summary: [Build] Add RAT exclusions for python docs Key: AVRO-3861 URL: https://issues.apache.org/jira/browse/AVRO-3861 Project: Apache Avro Issue Type: Bug

Re: [DISCUSS] Changing the Avro logo (revisited)

Already a year :O I added a comment to the JIRA and thanks again to Emma Kellam for stepping up here! We can and should probably add an attribution page to the the Avro website as part of this work. All my best, Ryan On Tue, Sep 19, 2023 at 1:42 PM Martin Grigorov wrote: > > Hi, > > My

[jira] [Created] (AVRO-3859) [Build][C#] build.sh clean fails to remove some C# files

Ryan Skraba created AVRO-3859: - Summary: [Build][C#] build.sh clean fails to remove some C# files Key: AVRO-3859 URL: https://issues.apache.org/jira/browse/AVRO-3859 Project: Apache Avro Issue

[VOTE] Release Apache Avro 1.11.3 RC1

Thursday, September 21th, 2023. [ ] +1 Release this as Apache Avro 1.11.3 [ ] +0 [ ] -1 Do not release this because... Best regards, Ryan Skraba [Countdown to vote]: https://www.timeanddate.com/countdown/to?iso=20230921T1159=1440

[jira] [Created] (AVRO-3858) [Build] Add some config to ./build.sh sign

Ryan Skraba created AVRO-3858: - Summary: [Build] Add some config to ./build.sh sign Key: AVRO-3858 URL: https://issues.apache.org/jira/browse/AVRO-3858 Project: Apache Avro Issue Type: Bug

Re: [DISCUSS] Release Avro 1.11.3

! If you have ideas on how we can simplify this process, I'd love to hear them. All my best, Ryan On Mon, Aug 14, 2023 at 2:14 PM Ryan Skraba wrote: > > Hey -- if nobody has any objections, I'd love to create the 1.11.3 this week! > > Committers, if you've done any change to mast

[jira] [Created] (AVRO-3855) [rust] lint/clippy fails in ubertool

Ryan Skraba created AVRO-3855: - Summary: [rust] lint/clippy fails in ubertool Key: AVRO-3855 URL: https://issues.apache.org/jira/browse/AVRO-3855 Project: Apache Avro Issue Type: Bug

Re: [DISCUSS] Release Avro 1.11.3

Hey -- if nobody has any objections, I'd love to create the 1.11.3 this week! Committers, if you've done any change to master that need to be in the 1.11.3 branch since the 1.11.2 release, make sure they've been cherry-picked and tested to the branch-1.11 :D I'll definitely go through the

Re: Specification of namespaces

Hello! I don't think SDKs should be generating namespaces that contain invalid names in any cases, and this is a bug in the Java SDK. One of the unfortunate consequences of "bad" names is that names are never _really_ necessary to deserialize/serialize data, so someone can be using the same

Re: [DISCUSS] Release maintenance and lifecycle

, with our already limited resources! What do you think? On Wed, Jul 19, 2023 at 12:09 PM Ryan Skraba wrote: > > I think we're all agreeing so far! Let's say we release 1.12.0 today, > the state would be > > master: 1.13.0-SNAPSHOT > branch-1.12: 1.12.1-SNAPSHOT > branch-

[jira] [Created] (AVRO-3819) [Java] Rationalize the system properties that limit allocation

Ryan Skraba created AVRO-3819: - Summary: [Java] Rationalize the system properties that limit allocation Key: AVRO-3819 URL: https://issues.apache.org/jira/browse/AVRO-3819 Project: Apache Avro

Re: Enum default not in canonical form

This is a bit weird, and it could be clarified. The "same" schema, of course, can be represented by different JSON text files: attribute order, ways to express the full name, inheriting full names, etc. The canonical form is always the "same" for the "same" schema and can be used to generate a

Re: Backwards incompatible API change to Python schema object "properties"

Hello! I think this sounds alright to me -- I noticed that your draft PR didn't delete the get_/set_props methods. Is there a mechanism we can use to mark them as deprecated for the length of one major release before removing them? I have no objection to improving the Python API :D Your PR is

Re: Implementing Python API Docs

Hey thanks for this work! Do you think the python doc generation stuff can be cherry-picked back to 1.11? That would be a neat addition to the website for the incoming 1.11.3! Building and deploying the website today is a really tricky problem... I think we're going to have to make some major

Re: [DISCUSS] Release maintenance and lifecycle

- 1.12.x receive from master new feature + CVE + bug fixes (1.12.n+1 should > > stay compatible with 1.12.n, so, it won't receive breaking change). > > - 1.11.x receive from master only CVE + bug fixes. > > > > thus allow users to adopt new feature even on minor released, and a

[DISCUSS] Release maintenance and lifecycle

A fixVersion up-to-date for someone to pick up the intention. That's just one suggestion that seems plausible to me! We can probably do better without much additional effort (on the limited resources we have). What do you think? All my best regards, Ryan On Mon, Jul 17, 2023 at 9:43 PM Ryan Skraba w

[DISCUSS] Release Avro 1.11.3

The regression from AVRO-3789 looks like it a sufficient regression to merit releasing 1.11.3, which should also cover some of the minor bumps necessary for the Rust SDK. Any objection to doing another while the branch-1.11 is still in a pretty releasable state? I would rather prioritize getting

[ANNOUNCE] Apache Avro 1.11.2 released

The Apache Avro community is pleased to announce the release of Avro 1.11.2! All signed release artifacts, signatures and verification instructions can be found here: https://avro.apache.org/releases.html This release addresses ~89 Avro JIRA, including some interesting highlights: C# -

Re: [VOTE] Release Apache Avro 1.11.2 RC1

to cmdline/IDE. > > > > On Mon, Jul 3, 2023 at 6:09 PM Ryan Skraba wrote: > > > > > Oh, I forgot to address Martin's comments here -- I was waiting to see > > > if there were any other "minor" issues that might accumulate and > > > justify a ne

Re: [VOTE] Release Apache Avro 1.11.2 RC1

ions to do the crate, so it's currently unchanged. We could probably consider Rust to be the "test" SDK for independent releases! All my best, Ryan On Mon, Jul 3, 2023 at 12:40 PM Ryan Skraba wrote: > > Thanks so much for taking the time to validate this release! I just > f

[VOTE][RESULT] Release Apache Avro 1.11.2 RC1

Hello everyone, With seven +1 (five binding) and no 0 or -1, I'm please to announce that the vote has passed to release Avro 1.11.2. I will start releasing artifacts to the various package managers and send the announcement within the week. Thanks everyone for your contributions! Ryan Skraba

Re: [VOTE] Release Apache Avro 1.11.2 RC1

st ran the java > > builds and looked through a few things, but looks OK to me. > > > > Dan > > > > > > > On Jun 27, 2023, at 3:32 AM, Ryan Skraba wrote: > > > > > > Hi everyone, > > > > > > I'd like to propose the

Re: [VOTE] Release Apache Avro 1.11.2 RC1

t; (dependency update) > > > - > > > > > > > > https://github.com/apache/avro/commit/1dcaf1d4dd07f8d590cb48241a68d5d8b07ff8d2 > > > (dependency update) > > > - > > > > > > > > https://github.com/apache/avro/commit/cdc2286677813ce2

[VOTE] Release Apache Avro 1.11.2 RC1

, Ryan Skraba [Countdown to vote]: https://www.timeanddate.com/countdown/to?iso=20230630T1159=1440

Re: Checks on Avro PR

Hello! I believe that the default policy (implemented by Infra) was to require a committer approval to launch CI on every PR. In the recent past, every *new* contributor (who hadn't been approved before) required one approval, and in the farther past no PRs required approval. I think we're

Re: [DISCUSS] Release Avro 1.11.2

timeline is to get those merged and > have a RC1 for the end of the week. Thanks everyone for your > extraordinary patience! > > All my best, Ryan > > > > > On Thu, May 25, 2023 at 9:25 PM Ryan Skraba wrote: > > > > Hey everyone -- May has been a pretty busy

[jira] [Created] (AVRO-3783) [Java] Deserialize byte lengths as LONG but limit to INT

Ryan Skraba created AVRO-3783: - Summary: [Java] Deserialize byte lengths as LONG but limit to INT Key: AVRO-3783 URL: https://issues.apache.org/jira/browse/AVRO-3783 Project: Apache Avro Issue

Re: [DISCUSS] Release Avro 1.11.2

everyone for your extraordinary patience! All my best, Ryan On Thu, May 25, 2023 at 9:25 PM Ryan Skraba wrote: > > Hey everyone -- May has been a pretty busy month for me, I just wanted > to get back here and assure people that I'm still working on > cherry-picking from master to

Re: [DISCUSS] Release Avro 1.11.2

think we would all love to hear them! All my best, Ryan On Fri, Apr 21, 2023 at 6:21 PM Ryan Skraba wrote: > > Hey! Thanks so much for the vote -- yeah, this is long overdue! > > My assumption was that the branch would be ready to be released at any > moment, but it looks like

Re: Map Key Uniqueness (Spec clarification)

Hello! You're correct that there is no guidance in the spec, and that conceptually an Avro map could be represented as an ordered list of (key, value) tuples. It's only an opinion, but I think the *best practice* for interoperability would be to avoid serializing duplicate keys. Whoever is

Re: [DISCUSS] Release Avro 1.11.2

m/FasterXML/jackson/wiki/Jackson-Release-2.15>. Is that > also your assessment? > > I'm keen to see a 1.11.2 "CVE clean" release also, so big +1 from a random > user. > > Kind regards, Eric > > On Mon, Mar 13, 2023 at 10:55 AM Ryan Skraba wrote: > &

[jira] [Created] (AVRO-3738) [Build][C#] The release build fails with .NET 7.0 target

Ryan Skraba created AVRO-3738: - Summary: [Build][C#] The release build fails with .NET 7.0 target Key: AVRO-3738 URL: https://issues.apache.org/jira/browse/AVRO-3738 Project: Apache Avro Issue

[jira] [Created] (AVRO-3737) [C] memcheck_test_avro_commons_schema is failing

Ryan Skraba created AVRO-3737: - Summary: [C] memcheck_test_avro_commons_schema is failing Key: AVRO-3737 URL: https://issues.apache.org/jira/browse/AVRO-3737 Project: Apache Avro Issue Type: Bug

[jira] [Created] (AVRO-3736) [Build][Ruby] The release build fails "bundle not found"

Ryan Skraba created AVRO-3736: - Summary: [Build][Ruby] The release build fails "bundle not found" Key: AVRO-3736 URL: https://issues.apache.org/jira/browse/AVRO-3736 Project: Apache Avro

[jira] [Created] (AVRO-3734) Integrate build with Apache Avro github actions / local build

Ryan Skraba created AVRO-3734: - Summary: Integrate build with Apache Avro github actions / local build Key: AVRO-3734 URL: https://issues.apache.org/jira/browse/AVRO-3734 Project: Apache Avro

[jira] [Created] (AVRO-3733) Migrate package names and artifacts to org.apache.avro namespace

Ryan Skraba created AVRO-3733: - Summary: Migrate package names and artifacts to org.apache.avro namespace Key: AVRO-3733 URL: https://issues.apache.org/jira/browse/AVRO-3733 Project: Apache Avro

[jira] [Created] (AVRO-3732) Code drop existing sources, updating headers, RAT, NOTICES, etc.

Ryan Skraba created AVRO-3732: - Summary: Code drop existing sources, updating headers, RAT, NOTICES, etc. Key: AVRO-3732 URL: https://issues.apache.org/jira/browse/AVRO-3732 Project: Apache Avro

[jira] [Created] (AVRO-3731) Integrate software donation of gradle-avro-plugin

Ryan Skraba created AVRO-3731: - Summary: Integrate software donation of gradle-avro-plugin Key: AVRO-3731 URL: https://issues.apache.org/jira/browse/AVRO-3731 Project: Apache Avro Issue Type

Re: Issues with website

Hey William Taylor, thanks for bringing these up -- we're in an odd state right now with the website where we have to manually release it (during an Avro release), but ... it's a complicated process likely to change! Thankfully, Martin has been working towards having auto-deployed artifacts and

Re: [DISCUSS] Release Avro 1.11.2

Please do not stop contributing to 1.12.0, of course! That should be the destination for the great new features that belong to a major release! All my best, Ryan On Sat, Mar 11, 2023 at 8:52 AM Oscar Westra van Holthe - Kind wrote: > > On th 9 mrt. 2023 22:14, Ryan Skraba wrote: > > > H

Re: [DISCUSS] Release Avro 1.11.2

%20AND%20status%20!%3D%20Resolved On Thu, Nov 10, 2022 at 7:37 PM Ryan Skraba wrote: > > We probably don't need to do an initial vote on this :D Fixing CVEs > is probably a compelling enought reason to do this! > > But if anybody thinks this is a bad idea, needs anything specif

Re: [DISCUSS] Java 8 compatibility?

This seems like something that an LTS version might serve well! For as long as I've used Avro, only the most recent version has active support, but we've talked about having more than one version. If we go this route, I'd be comfortable dropping Java 8 on Avro 1.12.x! I'd also be comfortable

Re: Release language modules separately

gt; > debate the other details as we go. > > > > On Thu, Jan 5, 2023 at 12:25 PM Tim Perkins wrote: > > > > > On Wed, Jan 4, 2023 at 1:15 PM Ryan Skraba wrote: > > > > > > > Maybe a good way to get to consensus would be to list the possible > >

Re: Deploy documentation via .asf.yaml

ov wrote: > > > I created https://issues.apache.org/jira/browse/AVRO-3686 > > > > AVRO-3651 can easily be solved by using https://avro.a.o for > > current/master instead of https://avro.staged.a.o. > > With the current pace of editing the docs (close to none) I th

Re: Release language modules separately

Hello! We've started and stopped this discussion a couple of times -- but it ends up getting a bit bogged down in details, and there's so much going on that we end on sticking with the status quo! I would love to have this discussion again though and come to a conclusion. We could be doing

Re: Possible bug with avro-js with binary serdes and schema resolution

Hey -- thanks for reaching out! This is the right place to reach out for JIRA account creation -- we're still adjusting to the new changes, but I can create an account for you. I'll send an email with some details to confirm. Ryan On Wed, Dec 7, 2022 at 10:26 AM Martin Grigorov wrote: > > Hi

Re: Deploy documentation via .asf.yaml

Oh yes!!! This would be an excellent change -- I was looking at the "nightlies.apache.org" used by Flink, but I think the staged approach is really nice. Have you taken a look at AVRO-3651 [1]? I was thinking this approach would make it possible to link to the "release" website artifacts, but

[jira] [Created] (AVRO-3682) [Build] Remove forrest from Avro build

Ryan Skraba created AVRO-3682: - Summary: [Build] Remove forrest from Avro build Key: AVRO-3682 URL: https://issues.apache.org/jira/browse/AVRO-3682 Project: Apache Avro Issue Type: Task

[jira] [Created] (AVRO-3681) [Python] GitHub actions failing with python 3.6

Ryan Skraba created AVRO-3681: - Summary: [Python] GitHub actions failing with python 3.6 Key: AVRO-3681 URL: https://issues.apache.org/jira/browse/AVRO-3681 Project: Apache Avro Issue Type: Task

[jira] [Created] (AVRO-3680) [Python] Allow disabling naming validation for interoperability

Ryan Skraba created AVRO-3680: - Summary: [Python] Allow disabling naming validation for interoperability Key: AVRO-3680 URL: https://issues.apache.org/jira/browse/AVRO-3680 Project: Apache Avro

Re: [DISCUSS][VOTE] Naming rules

> if desired* > Personnally, i like the idea to have mandatory name control you can't > deactivate, to ensure it won't generate bug (For Java code generation > mainly and to be able to separate name and namespace), but control > specification should be limited to ban names that would genera

[jira] [Created] (AVRO-3676) [Java] toString produces incorrect JSON for UUID

Ryan Skraba created AVRO-3676: - Summary: [Java] toString produces incorrect JSON for UUID Key: AVRO-3676 URL: https://issues.apache.org/jira/browse/AVRO-3676 Project: Apache Avro Issue Type: Bug

Re: [DISCUSS] Release Avro 1.11.2

.0. > 2.12.7 is not affected by the CVEs > > On Fri, Nov 4, 2022, 20:07 Ryan Skraba wrote: > > > It looks like there's been a couple of CVE fixes in dependencies that > > we might want to have! See AVRO-3656, and perhaps AVRO-3658 (not yet > > merged, bumping to jacks

Re: Programming languages for Avro

There's a couple of things we COULD talk about -- we've brought up versioning language SDKs separately from Avro core, allowing us to release them at a pace that corresponds to the bugs/contributions they receive. This adds quite a bit of complexity to the release, and we might have difficulties

Re: [DISCUSS][VOTE] Naming rules

Hello! Here's a couple of related JIRA from the past that we can use to inform our discussion: * AVRO-2659 demonstrates a pretty disastrous schema name that the Java SDK accepts. * AVRO-1022 (10 years ago!) has a somewhat tepid discussion about accepting UTF-8 that didn't quite get enough

[VOTE][RESULT] Accept donation of gradle-avro-plugin

212/3169109 > > > > > > Kind regards, > > Oscar Westra van Holthe - Kind > > > > Op ma 10 okt. 2022 18:58 schreef Ryan Skraba : > > > > > Hello everyone! > > > > > > The developer(s) of https://github.com/davidmc2

[DISCUSS] Release Avro 1.11.2

It looks like there's been a couple of CVE fixes in dependencies that we might want to have! See AVRO-3656, and perhaps AVRO-3658 (not yet merged, bumping to jackson 2.13, which might have breaking changes). We've been cherry-picking pretty nicely so the branch is in a pretty good state, with

[jira] [Created] (AVRO-3653) [build] Move off Travis CI

Ryan Skraba created AVRO-3653: - Summary: [build] Move off Travis CI Key: AVRO-3653 URL: https://issues.apache.org/jira/browse/AVRO-3653 Project: Apache Avro Issue Type: Task Reporter

[jira] [Created] (AVRO-3651) [web] Build and separate release-specific pages.

Ryan Skraba created AVRO-3651: - Summary: [web] Build and separate release-specific pages. Key: AVRO-3651 URL: https://issues.apache.org/jira/browse/AVRO-3651 Project: Apache Avro Issue Type

Re: gradle-avro-plugin seeking new maintainer

ng > so many gradle versions to keep the build times reasonable compared to > the user needs. > > Regards, > ismaël > > > > > > > > > On Mon, Oct 10, 2022 at 6:50 PM Ryan Skraba wrote: > > > > Thanks for the info David and Michael (and welcome for your f

Re: Proposed enhancement: configure mapping of AVRO namespace to Java packagename

This sounds like a neat feature -- there's a couple of places in the Java code where we create new instances of records (for example) by looking whether an Avro namespace and name -> Java package and class exist. Do you think this might be a complication? Regardless, having this feature wouldn't

[jira] [Created] (AVRO-3637) [python] Add validate_enum_defaults to schema parsing.

Ryan Skraba created AVRO-3637: - Summary: [python] Add validate_enum_defaults to schema parsing. Key: AVRO-3637 URL: https://issues.apache.org/jira/browse/AVRO-3637 Project: Apache Avro Issue

[VOTE] Accept donation of gradle-avro-plugin

Hello everyone! The developer(s) of https://github.com/davidmc24/gradle-avro-plugin are interested in finding a home for the Gradle plugin that generates Avro specific classes for the Java SDK. This is the equivalent of the Avro maven plugin that we currently maintain and would provide the same

Re: gradle-avro-plugin seeking new maintainer

t; > support some use cases that aren't part of his plugin or apache-tools. > > > > I'm not with that company anymore and am in a position where I could > > contribute some effort... > > > > Mike > > > > > > On Fri, Sep 9, 2022

Re: Avro Java Version

that require Java 8 into the > > modern > > > > age. Most notable is Spark; all versions 3.x work with Java 11. > > > > > > > > However, the oldest supported version seems to be 2.4.8, released in > > May > > > > 2021, which only

[ANNOUNCE] New PMC member: Martin Grigorov

Hi folks! On behalf of the Apache Avro PMC, I am pleased to announce that Martin Grigorov has accepted our invitation to become a PMC member. He has has been active, reliable and responsive to the community and a solid contributor to various SDKs, bringing well-thought out reviews and comments

  1   2   3   4   5   6   7   8   9   10   >