Previously in this thread I proposed to cut the release branch for Avro 1.10 on friday 15 May and let a period of 2 weeks after that for stabilization and then start the vote for the release.
However I (as other people in the project) at this moment have less time than expected so I would like to propose to postpone the branch cut and release two weeks to give us some short extra time to finish pending reviews and clean up stuff. New cut date May 29th. I hope this does not change many people plans, please let me know if you have any issues because of this and remember don't hesitate to ping me (hopefully) in advance if you want to discuss any release specific issue. Regards, Ismaël On Tue, Apr 28, 2020 at 10:02 AM Ismaël Mejía <ieme...@gmail.com> wrote: > > Hello everyone, > > As discussed previously [1] we intend to do the Avro 1.10.0 release on > May so I wanted to propose to cut the branch the next May 15th. The > idea is that in the following weeks we work hard on reviews and issue > triage and maybe the latest dependency updates. Once the branch is cut > we let then some days to stabilize the release branch (hopefully 1-2 > weeks) and then go with the vote. > > If you have issues you want to mark as critical to be part of the > release (e.g. security related or data corruption) mark them with the > Fix Version: 1.10.0 field in JIRA and more important if you have > issues that you think won’t be able to make it in time please > unmark/untag them or mark them as version 1.11.0 > > This is the list of open issues for the release, so please go ahead > and help us finish/triage them. > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20AVRO%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%201.10.0 > > Thanks, and good triage, don’t hesitate to email me or ping me in your > PRs./tickets to bring my attention on critical things for the release. > > Best, > Ismaël
