Hi, Thanks to Jack Klamer there are no known issues in the Rust SDK!
In the coming days I will add "Getting started" guide for Rust in the new website! Martin On Sun, Mar 20, 2022 at 12:46 AM Jack Klamer <jfkla...@gmail.com> wrote: > That PR has been merged thanks to the work of Martin! I believe there may > be more work to do in this vein but that PR covers some of the main > workflows that are affected. > > On Fri, Mar 18, 2022 at 1:40 PM Ryan Skraba <r...@skraba.com> wrote: > > > Hello Jack! How long do you you'll need? There's a lot of open PRs > > that we can evaluate in the meantime, so if it's worth it to delay a > > release a couple of weeks, then I have no objection! > > > > Ideally, I'd like to see more frequent releases, so that it's not such > > a big deal when someone's PR doesn't make it in for review reasons :/ > > > > In the meantime, there's still some things to do in the JIRA set for > > 1.11.1, I'll send another message if we start getting closer. > > > > All my best and thanks for your work! Ryan > > > > On Mon, Mar 14, 2022 at 4:22 PM Jack Klamer <jfkla...@gmail.com> wrote: > > > > > > Hey all, > > > > > > I would personally love to get in > > > https://github.com/apache/avro/pull/1602 as it contains a bug fix for > a > > > decently likely scenario. However it may take longer to get that in > than > > > the desired release time here, but I’ll do what I can to meet the > > deadline. > > > > > > Best, > > > Jack > > > > > > On Mon, Mar 14, 2022 at 10:11 AM Oscar Westra van Holthe - Kind < > > > os...@westravanholthe.nl> wrote: > > > > > > > Hi all, > > > > > > > > +1 for a minor release > > > > > > > > From what I can see, there's indeed enough for a new release. > > Especially > > > > the C# and Rust improvements merit a release. > > > > > > > > > > > > > > > > Kind regards > > > > Oscar > > > > > > > > On Tue, 8 Mar 2022 at 19:30, Ryan Skraba <r...@skraba.com> wrote: > > > > > > > > > Hello! > > > > > > > > > > There's about 150 issues that have been resolved[1] and cherry > picked > > > > > into branch-1.11 since the last release (including the one that > bumps > > > > > us off of the log4j CVE radar, even if we aren't vulnerable as is). > > > > > > > > > > We've been pretty rigorous with cherry-picking back to the > > branch-1.11 > > > > > so it would probably be a pretty easy release this time around! > What > > > > > do you think about starting the process? > > > > > > > > > > There's still a bit of work that I'd like to see in the website > and a > > > > > few open issues[2] targeted to 1.11.1, and many open PRs that might > > be > > > > > candidates. > > > > > > > > > > What do you think? Is it the right time to think about it? Is > there > > > > > anything blocking a new minor release? > > > > > > > > > > If you have an open PR or favourite JIRA that hasn't been > addressed, > > > > > don't hesitate to bring it up, or update the fixVersion. > > > > > > > > > > All my best, Ryan > > > > > > > > > > [1]: > > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%3DAVRO%20AND%20fixVersion%3D1.11.1%20AND%20status%3DResolved > > > > > [2]: > > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%3DAVRO%20AND%20fixVersion%3D1.11.1%20AND%20status!%3D%20Resolved > > > > > > > > > > > > > > > > > -- > > > > > > > > ✉️ Oscar Westra van Holthe - Kind <os...@westravanholthe.nl> > > > > > > >
