On Mon, Jul 10, 2023 at 10:30 AM Ryan Skraba <[email protected]> wrote:

> Welp, the release is already out, there's just the [ANNOUNCE] to do.
> I'll put this in the release notes as a known issue and prep for a
> 1.11.3.
>

The Rust SDK has been published too!
apache-avro 0.15.0 & apache-avro-derive 0.15.0 are available at crates.io !



>
>
> On Wed, Jul 5, 2023 at 5:25 PM Christophe Le Saëc <[email protected]>
> wrote:
> >
> > Felix Krull just found this issue
> > <https://issues.apache.org/jira/browse/AVRO-3789> in Java vresion (with
> the
> > PR to fix). So, as a regression, IMHO it should be merged before 1.11.2
> > release ?
> >
> > Le mer. 5 juil. 2023 à 14:55, Martin Grigorov <[email protected]> a
> > écrit :
> >
> > > Hi,
> > >
> > > Sorry for the late reply! I was on vacation without access to
> cmdline/IDE.
> > >
> > > On Mon, Jul 3, 2023 at 6:09 PM Ryan Skraba <[email protected]> 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 new RC with the Rust improvements!
> > > >
> > >
> > > I didn't find any other issues.
> > >
> > >
> > > >
> > > > What do you think about bumping and releasing the Rust crate
> > > > separately?  I didn't find the right instructions to do the crate, so
> > > > it's currently unchanged.  We could probably consider Rust to be the
> > > > "test" SDK for independent releases!
> > > >
> > >
> > > Sure!
> > > I will execute `cargo publish --all-features` in the Git tag for
> 1.11.2 !
> > > Just me and Ismael have permission to push to https://crates.io at the
> > > moment. If someone else from the PMC wants to be added to the team
> just let
> > > me/us know!
> > >
> > > Regards,
> > > Martin
> > >
> > >
> > >
> > > >
> > > > All my best, Ryan
> > > >
> > > > On Mon, Jul 3, 2023 at 12:40 PM Ryan Skraba <[email protected]> wrote:
> > > > >
> > > > > Thanks so much for taking the time to validate this release!  I
> just
> > > > > finished the highlights that I want to propose for the release
> notes.
> > > > > I hope I didn't miss anything major or anyone's favourite
> > > > > contributions, every single one is appreciated of course!
> > > > >
> > > > > I'll send out the result of the vote right away and start
> publishing
> > > > artifacts.
> > > > >
> > > > > C#
> > > > > - AVRO-3434: Support logical schemas in reflect reader and writer
> > > > > - AVRO-3670: Add NET 7.0 support
> > > > > - AVRO-3724: Fix C# JsonEncoder for nested array of records
> > > > > - AVRO-3756: Add a method to return types instead of writing them
> to
> > > disk
> > > > >
> > > > > C++
> > > > > - AVRO-3601: C++ API header contains breaking include
> > > > > - AVRO-3705: C++17 support
> > > > >
> > > > > Java
> > > > > - AVRO-2943: Add new GenericData String/Utf8 ARRAY comparison test
> > > > > - AVRO-2943: improve GenericRecord MAP type comparison
> > > > > - AVRO-3473: Use ServiceLoader to discover Conversion
> > > > > - AVRO-3536: Inherit conversions for Union type
> > > > > - AVRO-3597: Allow custom readers to override string creation
> > > > > - AVRO-3560: Throw SchemaParseException on dangling content beyond
> end
> > > > of schema
> > > > > - AVRO-3602: Support Map(with non-String keys) and Set in
> > > > ReflectDatumReader
> > > > > - AVRO-3676: Produce valid toString() for UUID JSON
> > > > > - AVRO-3698: SpecificData.getClassName must replace reserved words
> > > > > - AVRO-3700: Publish Java SBOM artifacts with CycloneDX
> > > > > - AVRO-3783: Read LONG length for bytes, only allow INT sizes
> > > > > - AVRO-3706: accept space in folder name
> > > > >
> > > > > Python
> > > > > - AVRO-3761: Fix broken validation of nullable UUID field
> > > > > - AVRO-3229: Raise on invalid enum default only if validation
> enabled
> > > > > - AVRO-3622: Fix compatibility check for schemas having or missing
> > > > namespace
> > > > > - AVRO-3669: Add py.typed marker file (PEP561 compliance)
> > > > > - AVRO-3672: Add CI testing for Python 3.11
> > > > > - AVRO-3680: allow to disable name validation
> > > > >
> > > > > Ruby
> > > > > - AVRO-3775: Fix decoded default value of logical type
> > > > > - AVRO-3697: Test against Ruby 3.2
> > > > > - AVRO-3722: Eagerly initialize instance variables for better
> inline
> > > > cache hits
> > > > >
> > > > > Rust
> > > > > - Many, many bug fixes and implementation progress in this
> > > > >   experimental SDK.
> > > > > - Rust CI builds and lints are passing, but there will
> > > > >   not be 1.11.2 versioned Rust artifacts as part of this
> > > > >   release.
> > > > >
> > > > > In addition:
> > > > > * Upgrade dependencies to latest versions, including CVE fixes.
> > > > > * Testing and build improvements.
> > > > > * Performance fixes, other bug fixes, better documentation and
> more...
> > > > >
> > > > > On Mon, Jul 3, 2023 at 9:50 AM Ismaël Mejía <[email protected]>
> wrote:
> > > > > >
> > > > > > +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 assume
> you we
> > > > can
> > > > > > do that once published).
> > > > > > Thanks for driving the release Ryan!
> > > > > >
> > > > > > Ismaël
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Sat, Jul 1, 2023 at 10:22 PM Daniel Kulp <[email protected]>
> > > wrote:
> > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > > Didn’t have much time to really dig in and test, mostly just
> 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 <[email protected]
> >
> > > > wrote:
> > > > > > > >
> > > > > > > > Hi everyone,
> > > > > > > >
> > > > > > > > I'd like to propose the following RC1 to be released as the
> > > > official
> > > > > > > Apache
> > > > > > > > Avro 1.11.2 release.
> > > > > > > >
> > > > > > > > The commit id is 44d1c4f221ccc4571a4b4b9edb023ed1e89354b7
> > > > > > > > * This corresponds to the tag: release-1.11.2-rc1
> > > > > > > > *
> https://github.com/apache/avro/releases/tag/release-1.11.2-rc1
> > > > > > > >
> > > > > > > > The release tarball, signature, and checksums are here
> (revision
> > > > r62648)
> > > > > > > > *
> https://dist.apache.org/repos/dist/dev/avro/avro-1.11.2-rc1/
> > > > > > > >
> > > > > > > > You can find the KEYS file here:
> > > > > > > > * https://dist.apache.org/repos/dist/dev/avro/KEYS
> > > > > > > >
> > > > > > > > Binary artifacts for Java are staged in Nexus here:
> > > > > > > > *
> > > > > > >
> > > >
> > >
> https://repository.apache.org/content/groups/staging/org/apache/avro/avro/1.11.2/
> > > > > > > >
> > > > > > > > This release includes ~90 Jira issues:
> > > > > > > > *
> > > > > > >
> > > >
> > >
> https://issues.apache.org/jira/issues/?jql=project%3DAVRO%20AND%20fixVersion%3D1.11.2
> > > > > > > >
> > > > > > > > I'll send a follow-up email with the notable highlights for
> each
> > > > > > > > language and SDK, but I wanted to give everyone a head start
> to
> > > > > > > > check their favourite fixed JIRAs and features!
> > > > > > > >
> > > > > > > > Please download, verify, and test. This vote will remain
> open for
> > > > at
> > > > > > > least
> > > > > > > > 72 hours. I would like to close at 11h59 UTC Friday, June
> 30th,
> > > > 2023
> > > > > > > >
> > > > > > > > [ ] +1 Release this as Apache Avro 1.11.0
> > > > > > > > [ ] +0
> > > > > > > > [ ] -1 Do not release this because...
> > > > > > > >
> > > > > > > > Best regards,
> > > > > > > > Ryan Skraba
> > > > > > > > [Countdown to vote]:
> > > > > > > >
> > > https://www.timeanddate.com/countdown/to?iso=20230630T1159&p0=1440
> > > > > > >
> > > > > > > --
> > > > > > > Daniel Kulp
> > > > > > > [email protected] <mailto:[email protected]>
> > > > > > > Talend - https://talend.com <https://talend.com/>
> > > > > > >
> > > > > > >
> > > >
> > >
>

Reply via email to