Hello! In order to get this moving, I propose cutting a branch for 1.11.0 tomorrow at noon UTC -- any non-blocking PRs and JIRAs that are not yet on master will have to wait.
Any specific objections? I'd like to propose a release candidate before the weekend. Please don't be discouraged if your feature or fix didn't make it in, I think we *should* start thinking about the next major or minor release immediately. There a few topics that have been discussed in the past that I'd like to see revisited and voted on after this release! All my best, Ryan [Countdown to branch]: https://www.timeanddate.com/countdown/to?iso=20211006T12&p0=1440 [Unresolved JIRA]: https://issues.apache.org/jira/issues/?jql=project%20%3D%20AVRO%20AND%20fixVersion%20%3D%201.11.0%20and%20status%20!%3D%20Resolved%20and%20status%20!%3D%20Closed [Releases, versioning and lifecycle]: https://lists.apache.org/thread.html/r3d42328e2e76ea238af09f7ea04a8765e5e9acf40f9f88913c4b1785%40%3Cdev.avro.apache.org%3E On Wed, Sep 29, 2021 at 10:49 AM Martin Grigorov <[email protected]> wrote: > > On Wed, Sep 29, 2021 at 11:16 AM Ryan Skraba <[email protected]> wrote: > > > There's two JIRA that I would really like to see finished as New > > Features for this major release: AVRO-2863 (necessary for android > > compatibility) and AVRO-3186 (necessary for Quarkus compatibility). > > The latter has a PR opened but I haven't had the time to test it out > > with Quarkus. If we can get these in, how do you feel about having a > > branch cut and an RC1 before the end of the week? > > > > If you have any open JIRA that aren't tagged 1.11.0 and that should > > be, please update them soon! If you see a JIRA tagged 1.11.0 that > > doesn't block the release, please update the Fix Version. I've > > created a 1.11.1 Version in JIRA so that we can push some fixes to the > > next minor release. I hate to see open PRs that just need a bit of > > attention to make their way into a major release, but I don't want > > this to drag on! > > > > I can't speak much for the Rust SDK at the moment. > > > > We definitely need to have some discussion on our versioning and > > release policies, but I'll open a separate thread for that. > > > > All my best, Ryan > > > > [Unresolved JIRA]: > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20AVRO%20AND%20fixVersion%20%3D%201.11.0%20and%20status%20!%3D%20Resolved%20and%20status%20!%3D%20Closed > > > > <https://issues.apache.org/jira/issues/?jql=project%20%3D%20AVRO%20AND%20fixVersion%20%3D%201.11.0%20and%20status%20!%3D%20Resolved%20and%20status%20!%3D%20Closed[AVRO-2863> > > > IMO the following two issues could be postponed: > - https://issues.apache.org/jira/browse/AVRO-3143 (I've already removed its > Fix version. Please let me know if I have to revert!) > - https://issues.apache.org/jira/browse/AVRO-2955 > > > > [AVRO-2863 > > <https://issues.apache.org/jira/issues/?jql=project%20%3D%20AVRO%20AND%20fixVersion%20%3D%201.11.0%20and%20status%20!%3D%20Resolved%20and%20status%20!%3D%20Closed[AVRO-2863>]: > > https://issues.apache.org/jira/browse/AVRO-2863 > > [AVRO-3186]: https://issues.apache.org/jira/browse/AVRO-3186 > > > > On Thu, Sep 23, 2021 at 9:20 AM Martin Tzvetanov Grigorov > > <[email protected]> wrote: > > > > > > Hi, > > > > > > On 2021/08/17 08:51:48, 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) > > > > > > Since there were no requests to keep something for 1.11.0 I'd suggest to > > move to next. > > > > > > > > > > > 2. There's quite a few open PRs that could possibly be merged with a > > > > bit of attention. > > > > > > Or they could be left for 1.12.0 which could be released soon after. > > > > > > > > > > > 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. > > > > > > I am learning Rust and I'd like to help here as much as I can! > > > > > > > > > > > 4. I'd love to see the GitHub actions build consistently green! We're > > > > getting there... > > > > > > It looks good now! > > > > > > Martin > > > > > > > > > > > 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 > > > > > >
