Hello again! I think we can safely say there's some community demand for an 11.0 release -- I've been going through tagged JIRA and PRs.
We're currently not in a bad state, but there's some compelling features and old PRs that should probably be included! If you have any opinions on features that should/shouldn't be included, now would be a good time to tag your JIRAs. There's also notably some C# and C++ PRs that could use a bit of attention. Any opinions on when we should target cutting a RC branch? I'd like to suggest sooner rather than later (early September). I personally don't mind doing several Release Candidates, but I understand that it can be a burden as well... it's not an RC when you know in advance it's not going to be satisfactory. Also a side note, I found out why we weren't autolinking JIRA -> GitHub PRs -- the githubbot had no permissions on our project. This should be fixed, but you might still need to manually link old PRs. Best regards, Ryan On Tue, Aug 17, 2021 at 10:51 AM Ryan Skraba <[email protected]> wrote: > > Hello all! We've had a minor release this year, 1.10.2 in March -- > this was a great step because it had a couple of fixed that were > necessary to bump Avro in some downstream projects. > > It looks like there's a bit of community interest (AVRO-3185 for > example) in having a 1.11.0 release. What do you think? What would > be necessary to be in a good state for a major release? > > 1. There's quite a few JIRA[1] tagged for 1.11.0 that still need > fixing (or moved to next release) > > 2. There's quite a few open PRs that could possibly be merged with a > bit of attention. > > 3. How are we for Rust? That would be a nice announcement, but IIRC > there's some massaging to do in order to get it into "as good a state" > as the existing rust alternative. > > 4. I'd love to see the GitHub actions build consistently green! We're > getting there... > > Anything else? > > All my best, Ryan > > [1]: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20AVRO%20AND%20fixVersion%20%3D%201.11.0%20and%20status%20!%3D%20Resolved%20
